Configuration & auth
Tokens rejected after deploy
The same API token works locally and fails in production.
Investigation brief
Trace a request through configuration loading and token validation.
Work-sample pack 01 Node.js / JavaScript
Five failures across the life of a request. Trace the evidence, fix the cause, and prove the system holds.
Free with an account. New here? Try a shorter guest lab first.
Start an investigation
Next investigation
Tokens rejected after deployAccepted fixes save your place. Each one unlocks a free debrief.
Configuration → resources → state → side effects. Start in order, or choose your failure.
Configuration & auth
The same API token works locally and fails in production.
Trace a request through configuration loading and token validation.
Resource lifecycles
A read API starts healthy, then queues requests and returns 5xx under load.
Follow a borrowed resource through successful and failing requests.
Cache isolation
An order endpoint returns another region’s data after a traffic burst.
Follow an ownership boundary across a repository and its cache.
Retries & idempotency
A checkout times out. The retry succeeds, but the customer is charged twice.
Reconstruct what happened on both sides of an ambiguous timeout.
Concurrency & recovery
A redelivered queue job races with another worker and applies its effect twice.
Reason about interleaving workers and recovery after a failure.
Curated from existing Buglyst labs. Fictional scenarios in isolated workspaces; no live production systems.
Choose relevant work samples and review the candidate’s checks, patch and explanation. These labs are public; candidates may have practised them.