Skip to content

SYS-1011

Rabt could not reach its queue and cache server

Why it happens

The connection between Rabt and its Redis server, which holds its background task queues, rate limits and cache, failed or did not answer in time (for example during maintenance), so this action did not finish. Work that Rabt has already saved is queued again automatically once the server is back.

What to do

Try again in a moment. If this keeps happening, send these details to Rabt support.

HTTP status
503
Retrying can help

All error codes