t1211: Add diagnostic actions log on parse failure for better observability#1843
t1211: Add diagnostic actions log on parse failure for better observability#1843marcusquinn merged 1 commit intomainfrom
Conversation
…bility (t1211) When run_ai_actions_pipeline receives a non-array response from the AI model, it now writes a dedicated parse-failure log to the actions log directory (actions-TIMESTAMP-parse-failure.md) in addition to the supervisor log warning. This makes parse failures visible in the same directory as successful action logs, making it easier to correlate failures with specific pulse cycles without having to grep the supervisor log. The core fixes (rc=0 on empty response, retry with simplified prompt, raw response logging) were already implemented by t1182/t1184/t1187/t1189/t1197/t1201. This PR adds the final observability improvement from the t1211 spec.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Thu Feb 19 00:13:48 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|



Summary
The three requirements from t1211 were already implemented by prior tasks:
This PR adds the final observability improvement: when
run_ai_actions_pipelinedetects a non-array response, it now writes a dedicatedactions-TIMESTAMP-parse-failure.mdlog to the actions log directory. This makes parse failures visible alongside successful action logs, improving debuggability without requiring supervisor log grep.ShellCheck: zero violations.