Monitoring and troubleshooting

When an instance is stuck, output looks wrong, or a task fails, use a fixed checklist instead of only scrolling chat.

First data to collect

• Instance name, time window, model used, and whether config or a big file just changed.
• Last failure message or error code in task or instance details; open logs if available; see the error-code topic in the sidebar.

Common directions

• Network or auth: API auth expiry, allowlists, callback URLs.
• Quota or throttling: plan and console alerts; reschedule or request capacity.
• Prompt or resource change: roll back to the last known-good version.

Escalation

• Repro steps and screenshots in a ticket or ops channel.
• For repeat failures, add a runbook or knowledge item to shorten the next fix.