Troubleshooting

Most of the time, a session that is not moving is waiting for something - usually you. The Notifications bell lists everything that is.

"No coding agent is set up" when I send#

The project has no agent yet. Iterada says so and opens the guide at its first step. Open Agent factory, then Agents, press Add beside the agent you use, then Configure and sign it in. Your text stays in the message box: send it again once an agent is there. See Agents.

Rate limit reached#

The agent's plan ran out for now. The session waits and resumes by itself when the limit resets, or straight away on the next agent in the project's order, if you have added one. Nothing is lost, and no message is posted in your name. Provider availability on the Agents tab shows when a limited agent can be tried again. A session that reads "Waiting to retry automatically" is paused the same way, for example after a provider outage, and resumes by itself. A wait like this, or any retry Iterada makes by itself, is not listed under Notifications.

An agent is not signed in#

An agent whose row on the Agents tab reads "no sign-in yet" has no login. Press Configure and add one under Sign-in. A login that failed shows why, and when it can be tried again, on the Subscriptions tab. Add it again from Configure if its sign-in has expired. Pi and opencode have no login of their own; they use the provider keys your installation passes to agent runs.

The change did not merge#

• "Waiting for your merge": the project's workflow has no Merge step, so each change waits for you. Press Merge at the top of the session.

• "Checks failed, so it was not merged": your tests still failed on the change after Iterada's own attempts to fix it. Ask the agent in the same session to fix them; the merge goes through once they pass.

• "Checks timed out after 4 hours, so it was not merged": no test failed, but each run of the checks ran out of its time, usually because the machine was busy. Iterada runs a check that ran out of time again by itself, waiting longer each time, and stops after four hours. Merge it yourself if you trust it, or send a message to work on it further.

• "Some variables need setup": the change needs a value only you have. Set it or press Skip under Notifications.

• A session that is part of a split waits for its sibling sessions to finish changing files, so they reach the default branch together.

The agent stopped with an error#

The session is marked "Conversation ended with an error". Send a message in the same session to pick the work up again - the agent continues on the same branch with what it already did. If it happens again, press Report incident under the reply, say what went wrong if you can and press Send report. Tick Include full logs and conversation history so the Iterada team can see what the agent did; on the Free plan they are always included.

The reply asked me something#

The agent stops at decisions that are yours to make: what the product should do, which service you already use. Press one of the buttons it offers, or answer in your own words; the session carries on from your answer.

Still stuck?#

Use the Feedback tab on the right edge of the screen, or write to contact@iterada.com. Say what you expected and what happened instead.