Troubleshooting and Empty States

Resolve common onboarding, missing-data and commercial-access problems.

AWS registration returns HTTP 400

Inspect the response body and request payload of the failed registration request. Common causes are invalid/expired onboarding intent, invalid IAM role ARN, missing required fields or validation failure. A CORS header being present is not evidence that CORS caused the 400. Never share a bearer JWT or ExternalId in support screenshots.

Overview shows dashes for monthly spend

Confirm the correct workspace, validated AWS connection, available CUR/Data Export, completed cost ingestion and authoritative allocation run. A connection alone will not create spend figures. Incomplete or delayed source coverage should be shown rather than replaced by zero.

Applications and workloads both show zero

Check Migration → Legacy Estate & Import. AWS inventory resources do not necessarily create business application records. Imported/created records must belong to the selected workspace.

No estimated optimization opportunity

Check enrollment/permissions for AWS Cost Optimization Hub and Compute Optimizer, the latest refresh job, scope and source observation time. A successful refresh may legitimately return no actionable recommendations.

Value Ledger is empty

A recommendation or application import does not create a verified outcome. Follow the governed action, customer implementation and verification workflow with evidence.

Migration asks to import an estate

Use CSV/XLSX or supported manual input, validate preview and commit. Check whether the current workspace contains the expected application records.

Subscription or Marketplace purchase does not activate

Review verified provider status, the linked workspace, entitlement freshness and required registration/claim steps. Do not create another direct checkout if the workspace is already Marketplace-paid. Contact support through the configured product support channel; never paste payment secrets or raw Marketplace tokens.