Skip to main content
Available in version 0.13.2 and later.
Transactions normally move from QUEUED to APPLIED, INFLIGHT, or REJECTED. In rare occurrences, transactions may get stuck in QUEUED for example after a worker crash, Redis issues, or enqueue failures. Queue recovery finds these transactions and re-enqueues them for processing.

​
How it works

Blnk now automatically checks for and recovers any transactions stuck in queue due to any number of reasons. You can also trigger recovery manually with the Queue Recovery endpoint. 
curl --request POST \
  --url 'http://localhost:5001/transactions/recover?threshold=5m' \
  --header 'X-blnk-key: <api-key>'
threshold defines how long a transaction must be QUEUED before it is considered stuck. With threshold=5m, Blnk recovers only transactions that have been waiting at least 5 minutes; anything newer is left alone.
Minimum value allowed: 2 minutes.

​
Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.
Tip: Connect to Blnk Cloud to see your Core data.You can view your transactions, manage identities, create custom reports, invite other team members to collaborate, and perform operations on your Core — all in one dashboard.Check out Blnk Cloud →