Canonical: https://botbento.com/usecases/diagnosing-failed-data-workflow-runs/
Format: Markdown representation of the public HTML page.

[Home](/) / [Use cases](/usecases/) / [Operations](/usecases/?category=ops)

Operations · Intermediate

# Diagnosing failed data workflow runs

Inspect execution logs, identify root causes for failing pipeline steps, and draft workflow repairs.

[Use with BotBento ](https://app.botbento.com/?ref=usecases&utm_source=botbento.com&utm_medium=usecases&utm_campaign=diagnosing-failed-data-workflow-runs)Copy promptShare[Markdown](/text/usecases/diagnosing-failed-data-workflow-runs/index.md)[العربية](/ar/usecases/diagnosing-failed-data-workflow-runs/)

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.
```

Copy

## Tools it uses

TerminalSlackGitHub

## Works with

BotBento

## Tags

- orchestration
- pipelines
- debugging
- incident-response
- devops

## Source

[kestra: Event Driven Orchestration & Scheduling Platform for Mission Critical Applications](https://github.com/kestra-io/kestra)
GitHub · checked 2026-10-15

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

By BotBento Editorial · Added 2026-10-15 · Updated 2026-10-15 · [Suggest a correction](/contact/)

## Related use cases

-

Operationsintermediate

## [Monitoring multi-step deployment workflows](/usecases/monitoring-multi-step-deployment-workflows/)

Track distributed deployment steps, health checks, and failure retries automatically

TerminalGitHubSlackDatabase
-

Operationsadvanced

## [On-call incident runbook investigator](/usecases/on-call-incident-runbook-investigator/)

Diagnose production alerts by querying metrics, reviewing recent commits, and drafting mitigations

DatadogGitHubSlackTerminal
-

Operationsintermediate

## [Orchestrating scheduled runbooks and pipeline jobs](/usecases/orchestrating-scheduled-runbooks-and-pipeline-jobs/)

Convert standalone scripts into coordinated pipelines, inspect task logs, and safely retry jobs

TerminalSlackGitHub