Skip to content
CasesNew Learn 30 Career · co-op History Leaderboard Log in
EN
English✓ Русский

Access required

HIGH Case 8 · 30 min

Orders accepted, fulfillment stalled

The API returns 202, RabbitMQ is reachable and the worker is running, but new orders are not fulfilled. Trace messages through acknowledgement and drain the queue without losing orders.

What the on-call engineer sees

  • Ready and Unacked grow in orders; a few initial orders have already been processed.
  • Restarting the worker briefly changes the symptoms, but the queue stalls again.

You need an account to take this incident. Registration is free and takes a minute: just a username and password, with no email or phone number. The case you completed as a guest will carry over.

Sign up Log in

Without an account, you can complete case 0, “Store unavailable” —a short introduction in a real console.

Prepare for this caseLearn ↗

Explore the relevant skills before practice. Lessons open in a new tab.

  • Timeouts and retries: avoid amplifying an outage14 min ↗
  • systemd: a service will not start12 min ↗
  • Controlled changes: validate, apply, roll back12 min ↗
All preparation for this case →
Site terms · Privacy policy · Cookie settings · privacy.prodisdown@yandex.ru · Find us on VK · Find us on TikTok

We use cookies and Yandex Metrica to analyze visits. Learning analytics for signed-in users are linked to their account. By selecting “Accept”, you agree to the terms of data processing.