Match symptoms to root causes

When a deployed Lambda misbehaves, a repeatable troubleshooting playbook beats guessing. The idea is to move from broad signals to the precise cause: confirm something is actually wrong, narrow down which symptom you're seeing, read the evidence the function left behind, identify the root cause, then apply and verify a fix. Put the five steps of the playbook in the order an experienced operator would follow them.