Skip to content

[Workflows] Document historical execution time-range filter #7646

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
nastasha-solomon wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[Workflows] Document historical execution time-range filter #7646

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions explore-analyze/workflows/authoring-techniques/monitor-workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,17 @@ Every execution begins with a trigger entry that shows how the run started, such

To review past runs, select the **Executions** tab, then click each run to see detailed logs. Workflow runs can be `Pending`, `In progress`, `Completed`, or `Failed`.

## Filter historical executions by time range [workflows-execution-history-time-range]

```{applies_to}
stack: ga 9.5+
serverless: ga
```

**Run again** and **Run step again** replay a past execution instead of triggering a new manual run. They reuse the input and context from an execution you select, which is useful for reproducing an issue or testing a step change against real prior data. The execution picker in these dialogs includes a time-range filter next to the selection list. The filter defaults to the last week through now, so you can narrow a long execution history down to the runs you care about.

When you open replay from a specific execution (for example, by selecting **Run again** or **Run step again** on that execution's details), Kibana anchors the range to it automatically: the end of the range becomes that run's start time, which covers the week leading up to it. If you then adjust the range so the selected execution no longer falls within it, Kibana clears the selection, and you need to choose a new execution before you can submit the replay.

## Troubleshoot errors [workflows-troubleshoot-errors]

When a workflow fails, open the failed execution from the **Executions** tab, then find the step with the error indicator. Expand the step to view the error message and to learn more about the root cause, such the input that caused the failure. After fixing an error, save the workflow before running it again.
Expand Down
Loading