Troubleshooting

I can't connect an integration, or it stopped working

Almost always this is an authorization or scope problem. OAuth grants expire, get revoked, or were approved with fewer permissions than the task needs.

• Disconnect the integration and reconnect it, granting the scopes the agent needs — declining a permission it requires will make later actions fail.
• Check the provider's own security/connected-apps settings; if the grant was revoked there, re-authorize from AgentCorp.
• Make sure you are connecting the right account (a shared team account vs. a personal one) for the work you want.
• Corporate providers sometimes require an admin to approve third-party apps — ask your IT admin if the connect flow is blocked.

Per-connector detail lives in the integrations guide.

The agent says it hit a step limit

Long-running tasks have a ceiling on how many steps (tool turns) they take in a single run — a deliberate guardrail for safety and cost. The agent stops gracefully, tells you where it got to, and does not lose its progress.

• Just say “continue” and it picks up where it left off.
• For very large jobs, break the request into smaller milestones so each fits comfortably within a run.
• Ask for a plan first on big tasks so the work is chunked from the start.

Everything paused / I'm getting a 402

An HTTP 402 Payment Required, or agents that stop starting new work, means the workspace balance has reached zero. Nothing is lost — billable work is simply paused.

• Add a top-up ($25 / $50 / $100) or upgrade your plan; the balance updates immediately and agents resume.
• If a task still reports insufficient credits right after a top-up, refresh — the balance can take a moment to reflect — then retry.
• Admins can review recent consumption on the billing screen to see where credits went.

Full detail in the billing guide.

An approval isn't appearing

When an agent needs to send something, an approval card should show the recipient and message body. If you do not see it:

• Check the situation room and your notifications — the approval may be waiting there rather than in the current chat.
• Make sure the task actually reached the send step; if the agent is still drafting, ask it to proceed.
• If you use a channel like WhatsApp, confirm notifications are enabled there so approvals reach you off the web app.
• Refresh the app; a stale session can occasionally hold back a freshly created approval.

WhatsApp won't link

Linking WhatsApp connects your number to your workspace so you can message Alex from your phone.

• Start the link from the same workspace you want to use, and complete it from the exact number you intend to message with.
• Send the confirmation message the flow asks for — linking isn't finished until you reply from WhatsApp.
• If messages don't arrive, re-run the link flow; a half-completed link is the usual cause.
• One number links to one workspace at a time — unlink before moving it to another.

A new teammate can't see the workspace

Right after someone accepts an invite, their membership takes a brief moment to provision before the workspace is fully available to them.

• Wait a minute and have them refresh or sign out and back in.
• Confirm they accepted the invite with the same email it was sent to.
• As an admin, check Members to verify the invite shows as accepted and the role is set.
• If it persists beyond a few minutes, reach support with the invitee's email and your workspace name.

Still stuck?

Head to the support guide for how to reach us and how to file a bug report that gets resolved fast. The FAQ also covers a lot of ground.