About 5 min read
When agents stop replying or time out
Typical causes of missing replies, rate limits, gateway connectivity, and how to capture details for support.
No reply in chat
- Check whether the agent is paused, out of credits on the provider side, or missing a required connector.
- Large prompts may hit context limits; split the task or summarize prior turns.
Rate limits
HTTP 429-style errors usually come from upstream model providers. Back off, reduce parallelism, or upgrade provider limits.
Gateway or channel issues
Agents that depend on a gateway process may stop responding if that service restarted or lost authentication. Health pages often surface the failing dependency first.
Related articles
- What to do right after you sign up — A short checklist after you create an account: confirm email, pick or wait for your workspace, and open the product for the first time.
- Workspaces explained — How a workspace relates to your company account, why you might have more than one, and where your agents and data live.
- Sign in, SSO, and launch links — How sign-in works with the control plane, branded workspace URLs, and secure handoff into your tenant runtime.
- Members, invites, and roles — Inviting colleagues, what new members should expect on first visit, and keeping access aligned with how your team works.
- Billing, plans, and invoices — Where billing is managed, how usage-related charges may appear, and how to get help when something looks wrong on an invoice.
- Help Center home