Get support
Use your existing AI-LAB contact or internal support channel for hosted ATFGraph support. Start with the relevant troubleshooting check; it often identifies an account, local installation or environment mismatch without a reinstall.
Who can help?
| Request | Start with |
|---|---|
| Join a team, change a member role or approve a team-owned request | The team owner or the approver named by atfg approvals --all. |
| Create a team or resolve a platform approval | The platform approver shown on the request. |
| A rollout cannot start, the service is unavailable or logs cannot be fetched | AI-LAB, with the deployment/release ID and the time of failure. |
| An SDK example or node fails locally | The node author first; include the failing build check when asking AI-LAB for SDK help. |
| Enable an integration, provider, protocol or hosting option | AI-LAB; see Platform capabilities. |
Collect a small diagnostic report
These commands inspect state; they do not deploy or run a node:
atfg --version
atfg doctor --local
atfg doctor
atfg whoami
atfg config show
atfg --team <team> --env dev status <node> --json
Run the last command only if a node is involved. If the problem concerns a run, collect its run ID from the original output or Console. If logs are available, add a short excerpt from atfg --team <team> --env dev logs <node> --since 30m --errors after checking it for sensitive input.
What to include
Copy this outline into your support request:
Problem and expected result:
Exact command or Console action:
Time and timezone:
Operating system and CPU architecture:
CLI version and installation method (Homebrew / npm / release installer):
Team, project, node and environment:
Release / deployment / approval / run ID, if returned:
Error message and relevant doctor/build check:
What changed since it last worked:
Include full IDs from --json where supported. Use a minimal input that reproduces the issue. Do not include tokens, secret values, session files or raw customer data. Review screenshots and logs before sharing them.
While waiting
Keep the failed release ID and the local source. Repeating an approval request or bumping a version to retry an unchanged release creates extra work without fixing the cause. When the service is recovered, use retry an existing release. If only Console is affected, check the same-computer sign-in and team/environment selection before reinstalling.