Operations · Intermediate
Diagnosing failed data workflow runs
Inspect execution logs, identify root causes for failing pipeline steps, and draft workflow repairs.
Use with BotBento Markdownالعربية
Opens BotBento. Paste the prompt into a bot; nothing is preconfigured.
- When something happensWorkflow execution failure signal
- ThenInspect task logs and diagnose error
- ResultRequest approval to post triage report
When an orchestrated pipeline execution fails, this bot pulls the run logs, traces the broken task step, and isolates the root cause. It prepares an incident summary detailing the faulty parameters and recommends declarative workflow adjustments before notifying the on-call engineer.
Prompt to start with
BotBentoRecommended
When a workflow execution error occurs, connect via terminal to retrieve task logs and stack traces. Determine whether the failure was caused by bad inputs, network timeouts, or schema mismatches. Draft a concise incident summary explaining the error and propose configuration or retry parameter updates. Always ask for user approval before posting notifications to Slack or opening pull requests on GitHub.