serverless-debugging

Missing serverless logs often stem from silent failures or runtime divergences in platforms like Supabase Edge Functions or AWS Lambda. This Skill diagnoses these gaps by gathering evidence across database, code, environment, and deployment layers to pinpoint root causes.

To debug non-triggering Supabase Edge Functions, inspect production deployments and verify log gaps. You can form hypotheses using database logs and diagnostic responses, iterating through evidence-driven debugging steps until the silent failure is resolved.

Diagnosing silent failures in AWS Lambda requires evidence-driven pattern analysis across code and environment layers. This approach uses safe logging alternatives like database logs and traces to identify mismatched runtime behavior without relying on standard console output.

Yes, you can debug Cloudflare Workers with missing console output by applying safe debugging alternatives. The workflow satisfies evidence-gathering requirements across deployment and environment layers to diagnose runtime behavior divergences effectively.

Yes, manus-mcp-cli is a required dependency to run the debugging workflows. It provides the necessary interface to execute scripts and reference materials for diagnosing missing logs and silent failures across serverless and edge function runtimes.

Traditional logging in serverless environments fails when functions are deployed but not triggering or when runtime behavior differs from expectations. These limitations necessitate pattern analysis and evidence gathering across database, code, and deployment layers to resolve issues.