Facts first. Then hypotheses and verification.
Provide permitted logs, symptoms and recent change context. Ask CodeGryphon to reconstruct the timeline and suggest safe next checks.
Example: errors after a timeout change
Some requests fail after a configuration update. Sanitized logs and the diff are available.
- Reconstruct the timeline and affected operations.
- Compare timeouts, retries and error handling in code.
- Propose checks for hypotheses and measures to prevent recurrence.
What you get
A timeline, ranked hypotheses and a verification plan for the incident responder.
Gather evidence
Specify time, environment, affected operations and observed errors. Limit context to relevant data and remove unnecessary personal information and secrets.
Test possible causes
Compare events with code and configuration. For each hypothesis, identify a supporting signal, a way to check it and evidence that would disprove it.
Capture the outcome
After recovery, prepare a review, corrective changes and regression checks. Production actions require a deliberate team decision and appropriate access.
Start with your team's project
Download Desktop, connect your project and start with a task whose result you can verify.