DebugMidBackendAuto-graded

Find and fix an orders service throwing 500s

The orders service has returned 500s since a config change went out: find the cause in the logs and get errors back to zero.Checkout on the orders service started failing with 500s right after a config change, and an alert fired. You have the incident note, the access and error logs, and a metrics dump from the bad window. Find the cause, patch server.py and get the 5xx rate to zero. Checkouts that work today must keep working.

30 min

python

Start lab

You're done when

The checkouts that were failing now go through, and the 5xx rate is zero.
Checkouts that already worked still return the correct total.
The fix targets the cause you found in the logs and metrics, so similar requests the logs do not show stop failing too and the same failure cannot come back.

What it measures

Reading the evidenceUsing the logs and the metrics dump together to find where the fault is.

Root-cause debuggingReproducing the failure and tracing it back to its cause.

Closing the incidentChecking that the error rate really reached zero and leaving a guard against a repeat.

Your environment

Terminal + editorA full shell in the browser

Claude CodePre-authenticated, no key setup

Isolated microVMYours alone, wiped afterwards

Start this lab

30 min

Start labYou'll sign in to Anthropos to start. The lab opens in a private cloud workspace with Claude Code ready to use.

AI Labs is part of Anthropos Workforce. Not on your plan yet? Book a demo