Fix a run or a queue
A run failed, a queue is waiting, the phone AI hit its limit: find what you see and fix it.
Find what you see below. Before you start the same work again, look at what the phone already did: a failed run may have done part of the job.
The fastest first step: ask your assistant "why did my run fail?". It can read the run, its steps and its errors for you.
Quick fixes
| You see | Do |
|---|---|
| A run says Finished with an issue | Find the failed step |
| OpenCode Go's … usage limit was reached. Try again later. | Wait, or switch the model |
| A queue says Waiting for … | Read the reason |
| A queue item says AI adapter error, Proxy unavailable or Worker unreachable | Fix the cause, then re-queue |
| This queue is still a draft and cannot be opened here. | Ask your assistant to finish it |
| A run says Paused for admin | Ask the admin to look at it |
| You pressed a button and nothing seemed to happen | Check before you press again |
A run finished with an issue
-
Left menu → My Runs.
-
Press the run that says Finished with an issue.
-
Under Steps, press Filter attempts → Failed → apply.
-
Press the first failed step. Read its error and look at its screenshot.
-
Fix what the error names, using the table below.
-
Ask your assistant to start the run again.
| The error is about | Do |
|---|---|
| The phone AI or its limit | OpenCode Go usage limit was reached |
| The phone being offline or not ready | Fix PC Agent and iPhone connection |
| The app on the phone (logged out, a pop-up, an update) | Open the app on the iPhone, clear the pop-up, then run again |
| An account or a post | Ask your assistant to check that account or post |
Fixed when: the next run says Finished successfully.
A failed step can be retried inside the same run. Look at the run's overall result, not only one step.
OpenCode Go usage limit was reached
The run failed with OpenCode Go's five-hour usage limit was reached. Try again later. (or weekly, monthly). Your phone AI plan has limits; you used one up.
- Five-hour limit: wait a few hours, then run again.
- Weekly or monthly limit: switch the model, or wait.
To switch the model:
-
Left menu → AI Adapters.
-
On your OpenCode Go adapter, press Edit.
-
In Model, choose the other model: GLM 5.3 Flash or DeepSeek 4.1 Flash Free.
-
Press Save adapter, then Test.
Fixed when: Test passes and the next run gets past the AI step.
Using several phones at once uses the limit up faster. One Go Plus plan is enough for about 2–3 phones running 24/7. See Connect phone AI.
A queue is waiting
-
Left menu → Queues → open the queue.
-
Read the reason it shows.
| You see | Do |
|---|---|
| Waiting for a ready device | A phone is offline or not ready: Fix PC Agent and iPhone connection |
| Waiting for device … | That one phone is busy or offline. Check it in Devices |
| Waiting for a free execution slot | Other work is still running. Wait |
| Waiting for resource capacity | An account is busy in another run. Wait, or ask your assistant which run holds it |
| Waiting for access approval or Waiting for access renewal | Your Titan access is off or expired. Ask the admin |
| The queue says Paused | Press Resume if you want it to continue |
Fixed when: the queue says Active and items move.
A queue item failed
-
Queues → open the queue → find the item that failed. Read its reason.
| Reason | Do |
|---|---|
| AI adapter error | Check AI Adapters: press Test on the adapter. See OpenCode Go usage limit was reached |
| Proxy unavailable | The proxy is down or wrong. Ask your assistant to check it, or pick another in Proxies |
| Worker unreachable | The phone went offline: Fix PC Agent and iPhone connection |
| Run failed | Open the run: A run finished with an issue |
- After the fix, look at the phone: did it already do part of the job?
- Press Re-queue on the item to try it again.
Fixed when: the item says Succeeded.
The queue is still a draft
This queue is still a draft and cannot be opened here. Your assistant prepares queues; a draft is not finished yet.
- Ask your assistant: "finish my draft queue and make it ready".
- Queues → the queue now says Ready → open it → press Play.
Fixed when: the queue says Active.
Nothing happened after you pressed a button
The request may have gone through even if the page did not show it yet. Pressing again can start the same work twice.
- Wait a minute. Reload the page.
- Check My Runs and Queues: is the work already there?
- Still not sure? Ask your assistant: "did my last run start?".
Stopping work
| You want | Press |
|---|---|
| Stop one run | Cancel run on the run |
| Stop a queue for a while | Pause (Soft pause lets current work finish; Hard pause stops it now) |
| Stop a queue for good | Stop |
Closing the website does not stop anything: the phones keep working. Stopping does not undo what the phone already did in an app. See Watch your runs.
Still stuck
Ask your assistant: "why did my run fail? show me the first error". Still stuck? Contact support with the run ID.