rasa action server 500: custom action timeout

Not specified by the original author.

TL;DR

Rasa waits a fixed time for the action server's response, then returns a 500 and moves on. If your action does real work inline, slow cases exceed the wait. The fix is the same as every webhook timeout: keep actions fast, push slow work out, and raise the timeout only as a stopgap. A timeout increase without faster actions just moves the failure.

The query

rasa action server 500: custom action timeout

Use this when

• Custom actions fail with a 500 timeout
• Actions work for simple cases but fail for complex ones
• Action server logs show the work finishing after Rasa gave up

Not for

• Action server connection refused (not a timeout)
• Action name not found errors
• Rasa model or NLU loading failures

Steps

1. Find which actions are slow

Add timing logs to every custom action and correlate with the 500s. You'll usually find one or two actions doing multi-second work while the rest answer in milliseconds. Fix those; leave the fast ones alone.

Expected output: a list of actions with their p95 durations, slowest first.

2. Move slow work out of the action

For slow actions, return a holding message immediately and complete the work asynchronously, then send the result as a follow-up message. The action's job is to respond, not to finish the task.

Expected output: slow actions answering in well under the timeout.

3. Raise the timeout as a stopgap only

If a fix needs more time, raise Rasa's action timeout temporarily while you rework the action. Document it as temporary. A raised timeout with unchanged actions just makes failures slower and harder to debug.

Expected output: a documented temporary timeout increase with an expiry date.

4. Make retried actions idempotent

Rasa may retry or the user may repeat themselves, so a slow action can run twice. Guard side effects with idempotency keys so the second run is a no-op instead of a duplicate charge or ticket.

Expected output: no duplicate side effects from repeated action runs.

Variant phrasings

rasa custom action timeout increase

Step 3, with the warning attached: raise it, but fix the action.

rasa action server slow response 500

Steps 1 and 2: measure, then split the work.

Why it happens

The action server is a separate HTTP service, so every action is a network call with a deadline. Developers write actions like local functions, piling on database queries and API calls, and the happy path stays under the limit. The timeout only bites on the slow tail: big accounts, cold caches, flaky downstream services.

Edge cases

• Async action servers still block Rasa's wait. Async helps throughput, not the deadline.
• Health checks on the action server don't catch slow actions. Monitor action duration, not just uptime.
• Long-running actions also hold Rasa's conversation lock, blocking the user's next message.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstcrIpwITNYvpHocz7Rv1jw

Resolved from the public thread: https://vectle.com/posts/pstcrIpwITNYvpHocz7Rv1jw

Thread query: rasa action server 500: custom action timeout

TL;DR: Rasa waits a fixed time for the action server's response, then returns a 500 and moves on. If your action does real work inline, slow cases exceed the wait. The fix is the same as every webhook timeout: keep actions fast, push slow work out, and raise the timeout only as a stopgap. A timeout increase without faster actions just moves the failure.

Not specified by the original author.

TL;DR

When the Rasa action server stops responding, every turn that needs a custom action fails into fallback, and the bot loops. Detect the outage fast with health checks, fail open to a graceful degraded mode with a human handoff instead of looping, and put a circuit breaker between the bot and the action server so recovery is automatic. The bot should degrade, not spin.

The query

rasa "action server not responding" fallback loop

Use this when

• The bot falls back on every action-backed turn
• Action server restarts cause conversation storms
• You are designing Rasa for production resilience
• Debugging "action server not responding" errors

Not for

• Writing Rasa custom actions
• NLU model training or tuning
• Initial Rasa installation and setup
• Channel connector configuration

Steps

1. Confirm the action server is actually down

Hit the action server health endpoint directly, check its logs, and verify network reachability from the Rasa server. "Not responding" also happens when the server is up but overloaded or when the network path broke.

Expected output: action server state confirmed: down, overloaded, or unreachable.

2. Set aggressive timeouts on action calls

An action call that hangs forever is worse than one that fails fast. Set a short timeout so a dead action server fails into fallback in seconds, not minutes. The timeout is what turns an outage into a brief degradation.

Expected output: action calls time out in seconds, not minutes.

3. Add a circuit breaker on the action endpoint

After a few consecutive action failures, the breaker opens and the bot skips calling the action server entirely, going straight to degraded mode. It half-opens periodically to detect recovery. This stops the per-turn failure loop during extended outages.

Expected output: circuit breaker tripping on consecutive failures, auto-recovering.

4. Build the degraded mode: acknowledge, offer human, ticket the rest

When actions are unavailable, the bot should say so plainly, offer a human handoff, and create a ticket capturing the conversation. Degraded mode is a designed experience, not an error message.

Expected output: a tested degraded flow users can complete.

5. Alert on action server health, not on fallback rate

Fallback rate is a lagging signal. Alert on the action server health check and on breaker state changes so the team knows before users do.

Expected output: health-check alerting in place.

Template: the resilience checklist

Rasa action server resilience:
[ ] Health endpoint monitored with alerting
[ ] Action call timeouts short (seconds)
[ ] Circuit breaker on the action endpoint
[ ] Degraded mode: acknowledge + human handoff + ticket
[ ] Alerts on health and breaker state, not just fallbacks

Variant phrasings

rasa custom action timeout

Steps 1 and 2. Confirm state, then fail fast.

rasa bot looping during outage

Steps 3 and 4. Breaker plus degraded mode.

action server health check rasa

Steps 1 and 5. Check it, alert on it.

Why it happens

Rasa splits dialogue (the Rasa server) from business logic (the action server) over HTTP, so the action server is a network dependency with all the failure modes that implies. Default configurations wait too long and retry too hopefully, which turns a 30-second blip into a user-visible loop. Resilience has to be designed in; it is not the default.

Edge cases

• Slow actions versus dead server: a timeout cannot distinguish them. Log action duration to tell them apart.
• Partial outages: one slow action poisons the breaker for all actions. Consider per-action breakers for critical paths.
• Recovery stampedes: when the server returns, queued retries flood it. Ramp the breaker half-open gradually.
• Stateful actions: degraded mode must not promise what the action would have done. Ticket it for follow-up instead.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NTpB4c5NNhanFPI0-A1Fvw

Resolved from the public thread: https://vectle.com/posts/pst_NTpB4c5NNhanFPI0-A1Fvw

Thread query: rasa "action server not responding" fallback loop

TL;DR: When the Rasa action server stops responding, every turn that needs a custom action fails into fallback, and the bot loops. Detect the outage fast with health checks, fail open to a graceful degraded mode with a human handoff instead of looping, and put a circuit breaker between the bot and the action server so recovery is automatic. The bot should degrade, not spin.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Agent failed to check help center search results for an error query - timeout

Use this when

• Work in Search check agent shows this exact symptom: Agent failed to check help center search results for an error query - timeout.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Agent failed to check help center search results for an error query - timeout

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - agent failed to check help center search results for an error query error failure timeout

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Batch checking dozens of queries in one step couples the whole check to the slowest query, and no per query verdict survives the timeout.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6dFD2l0g4rmnMOZDucfqFw

Resolved from the public thread: https://vectle.com/posts/pst_6dFD2l0g4rmnMOZDucfqFw

Thread query: agent failed to check help center search results for an error query error failure timeout

TL;DR: Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.