Uh oh!
There was an error while loading. Please reload this page.
fix(backend): log failedReason when connection sync job fails - #1012
Conversation
The error message from a failed connection sync job was being stored in the DB but never surfaced in the logs, making it impossible to diagnose failures without querying the database directly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThis PR enhances error logging for failed connection sync jobs by capturing and displaying the actual failure reason instead of a generic message. Changes include updating the logging statement in the connection manager and documenting this fix in the changelog. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
Summary
job.failedReason) was stored in the DB but never printed to the logs"Failed job ... Failing job."message with no diagnostic information, even withSOURCEBOT_LOG_LEVEL=debug🤖 Generated with Claude Code
Summary by CodeRabbit