AWS Lambda: Phantom Retries — When Logs Multiply but Events Don’t Exist

AWS Lambda: Phantom Retries — When Logs Multiply but Events Don’t Exist # aws # lambda # devops # cloud Phantom retries can make a stable system look unstable Problem Your logs show the same Lambda event twice. The same RequestId appears again. CloudWatch metrics show two invocations where you expected one. You check your SQS queue or Kinesis stream — and there’s no duplicate message. No second trigger. Nothing out of the ordinary. Welcome to Phantom Retries — the haunting illusion of multiple Lambda executions that never actually happened. In this scenario, Lambda appears to “retry” work that it never re-received, leaving engineers chasing ghosts in their logs. Clarifying the Issue Phantom retries occur when signals, not actions, repeat. Lambda’s event model is at-least-once delivery , which means retries can happen — but what often looks like a retry is instead the result of lag, visibility timeout overlaps, or duplicate reporting at the monitoring...