Skip to main content

Troubleshooting

When a task does not go as expected, the agent says why in the Linear thread, and the task card on the Workflow board shows a stop reason with What is needed. Find the message or reason below.

The agent does not respond​

  • "The agent is off for this workspace." The agent has not been turned on for your workspace yet. Contact ThriveOnDev at info@thriveondev.com. The Workflow board shows Agent off in this case.
  • No reply at all. Check that the issue is in a Linear team your workspace works in (Settings → Linear → Choose teams) and that you assigned, delegated or mentioned the ThriveOnDev agent, not a person.
  • "Agent access denied" or "Message was not accepted". This usually means you don't have permission to give tasks yet. Ask an owner or admin to turn on Can give tasks for you. See Team and roles.

The agent couldn't be started​

Most start problems are setup problems. Open the task card and follow Open Settings:

Stop reasonWhat is needed
AI access not connectedAdd AI access for the agent this task uses. See Add your AI access.
AI access rejectedRemove your access and add it again.
Repository not allowedAn owner or admin adds the repository under Settings → GitHub → Choose repositories.
Setup incompleteFinish the station Settings marks.
Model not availableChoose another alias, or ask an owner or admin to change the developer or reviewer agent.
Agent didn't startStart the task again. If the agent says "Contact support to check the startup failure", write to info@thriveondev.com.

If the agent asks for Repo: owner/name and Base branch: branch, the issue does not point to exactly one allowed repository. Add those two lines to the issue description.

The task waits in the queue for a long time​

The queued comment in Linear names the reason and the position. Usually every slot in your workspace is busy. Tasks start by themselves as others finish. To free a slot, cancel tasks you no longer need in the To do list. See Queue and capacity.

The review keeps rejecting the change​

After three automatic fix-review rounds, the agent posts "Automatic fix-review paused." and stops. The issue and the review disagree, or the task is too big. Clarify the acceptance criteria in the issue, or split it, then comment /fix-review. Or fix the pull request yourself and comment /review. See Review loop and human approval.

CI fails or the pull request conflicts​

At release, failing CI or a conflict with the base branch sends the task back to fix review. The agent fixes the problem and merges the base branch in when needed, up to three times per task. If checks are still running, the task waits and continues by itself.

If it keeps failing, fix the cause or re-run flaky checks in GitHub, then comment /release or /fix-review.

AI usage runs out​

  • AI credits used up or AI usage limit reached: the provider account behind the AI access has no usage left. Top it up or wait for the limit to reset, then start the task again.
  • "Access needs to be renewed": add your AI access again. For Codex, paste a fresh auth.json.
  • AI provider unavailable: the provider is down. The task waits and continues by itself.

The task reached its time limit​

A run stops after 5 hours. Split the issue into smaller ones that each fit in one pull request. See Write issues an agent can finish.

The task is too large​

Task too large means the change does not fit in one run. Split it into several issues and connect them as blocking issues in Linear.

Still stuck​

Write to info@thriveondev.com with the Linear issue link, or check the system status.