Support
Common issues and how to resolve them. If your issue is not listed here, contact support@turbofinops.com or check the FAQ.
Fastest support path
Include the affected scope, connection name, action or receipt ID, scan job ID, and exact error message.
Verify the key values have no leading or trailing whitespace. For AWS, confirm the IAM user has programmatic access. For Azure, ensure the client secret has not expired. For GCP, paste the full JSON key file contents.
The App Registration must have the Reader role assigned at subscription level, not only resource group level. Azure role assignments can take 2-5 minutes to propagate.
Confirm the service account has Viewer on the correct project and that required APIs are enabled, including Compute Engine, Cloud Resource Manager and Container APIs.
Check that at least one scope is active, the external ID is correct, and credentials include the relevant describe/list permissions for the expected resource types.
This can happen during provider rate limits, transient network errors or large scans. Re-run the scan from Dashboard > Scans. If recurring, send support the scan job ID.
That can be valid if resources pass the enabled rules. Review Resources for inventory data and check domain dashboards for score context.
Confirm the scanned scope has cost-bearing resources and daily cost ingestion is available. Some clean environments will show a no-waste state instead of forced recommendations.
Receipts verify after the configured 7, 14, and 30 day windows. Check that daily cost rows exist for the resource and that the action baseline was captured before execution.
Review the receipt notes and observed daily cost. Inconclusive means the cost signal was not strong enough; regressed means post-action cost moved the wrong way and should not count as verified savings.
Actions in manual approval mode need an Admin or designated approver. Confirm notification settings and approve from Dashboard > Actions.
The conflict guard blocked execution because of IaC ownership, freeze windows or policy protection. Review the conflict reason before overriding.
Confirm the policy is active, the timezone is correct, the selected resources are current, and credentials include provider start/stop permissions: AWS EC2 StartInstances/StopInstances, Azure VM start/deallocate, or GCP compute.instances.start/stop. Basic scheduling uses cloud APIs and does not require a TurboFinOps agent on the VM.
Verify the Jira connection is saved and tested, the project key exists, and the API token has Create Issue permissions.
Verify the webhook URL in Dashboard > Integrations > Notifications, test the channel, and confirm the webhook was not revoked in Slack.
BYOAI requires a valid provider key. AI Explain, Plan and Summary are available from Professional; AI usage metering is Enterprise-only.
Check the user role in Settings > Users. Some receipt exports, automation, AI attribution, and enterprise controls are plan-gated, so compare the plan with Billing and the public pricing page.
Log out and back in to refresh session entitlement context. If Billing shows the upgrade but features remain locked, contact support.
Scan jobs are plan-gated monthly: Free includes 30 scan jobs, Professional includes 90, and Enterprise is unlimited.
Still need help?
Email support@turbofinops.com with a description of the issue, your plan, the affected scope or connection name, and any error messages, action IDs, receipt IDs or scan job IDs you can share. For security issues, use security@turbofinops.com.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.
