Most of the time a mission that looks "stuck" is actually waiting on you. Here is how to diagnose and unblock the common cases.
1. It is waiting at an approval point
The most common reason a mission pauses is that it hit one of the five approval points: money over a cap, a public claim, customer data leaving the boundary, a production-touching change, or an audit-trail edit. Check your approval queue. Each pending approval shows the recommendation, the rationale, and the alternatives. Click yes or no and the mission resumes on that branch.
2. It is waiting on a clarifying answer
At the start of a mission the CEO agent asks up to two clarifying questions, and nothing executes until the brief is confirmed. If a mission has not started, open it and check whether it is waiting for you to answer a question or confirm the brief.
3. It hit a token cap
If your AOS Credits balance reached a hard cap, work pauses rather than overspending. The mission will surface in your founder summary. Top up credits or raise the cap, and the work continues from where it paused. Nothing is lost.
4. A dependency or integration is not connected
Integrations are walled off by default. If a mission needs a tool you have not granted access to, it cannot proceed. Connect the required integration, then resume the mission.
5. The mission genuinely failed
If something went wrong, the mission surfaces in your founder summary with the rationale. From there you decide whether to retry, pivot the approach, or kill it. The evidence trail shows exactly where it stopped and why.
Can I pause a mission myself?
Yes. You can pause any mission mid-flight from Mission Control and resume it later. Pausing does not lose progress.
Still stuck?
Open a conversation from the in-app support panel or email us, and include the mission name. The evidence trail gives us everything we need to see what happened.