SYS-1005
service is failing: Rabt has paused requests to it
Why it happens
Recent requests from Rabt to service kept failing or timing out, so Rabt stopped sending it new requests for a short time to let it recover, and did not run this action. Rabt tries again automatically after a short pause; queued work (such as messages waiting to be sent) stays queued and is sent automatically when the service responds again.
What to do
No action is needed for queued work. For this action, try again in a few minutes. If it keeps failing, check the Rabt status page or send these details to Rabt support.
- HTTP status
- 503
- Retrying can help
- Placeholders
- service