Visual workflows
Inspect workflow runs and diagnose failures
Workflow run history is the record of executions and their outcomes. It connects a configured process with evidence of what actually happened.
Updated
By Kition Docs
Verified against Kition 0.2.0 (7d49036f) on 2026-11-06
Find the execution before changing the process
When an expected output is missing, first locate the relevant run. Distinguish a workflow that never started from one that started and failed or was skipped by a filter. Editing action settings will not fix a disabled workflow, and changing a schedule will not fix an invalid recipient.
Compare the run with the input and settings active at that time. If you changed a field or connection after the failure, do not assume that the old run used the new values. Successful runs are kept for 14 days and failed runs for 30 days.
Investigate a failed run
- Open Workflows, look for a workflow marked Failing, and open its Run History tab.
- Filter runs by Sent, Failed, or Skipped and find the run for the expected record or time.
- Expand it to read the Record, When, Error, and Body details, and use View node to open the step that failed.
- Check the actual destination for partial output before deciding to retry.
- Correct the setting or connection, then use Retry, which runs it again as a new run, and verify the result.
Separate common failure categories
| Observation | Investigation |
|---|---|
| No matching run | Trigger, enabled state, required fields, and schedule |
| Skipped run | The filter conditions and the record values |
| Connection failure | Selected email connection and its current credential |
| Reported success but wrong output | Business intent, substitutions, and destination |
| Partial output | Completed effects before any retry |
Retry without duplicating completed work
A failed sequence may already have completed an earlier action. Review existing records or messages before retrying. Do not assume that failure means nothing happened or that a retry deduplicates every external effect.
For support, capture the installed version, workflow purpose, a redacted error, and the step where the failure appeared. Remove message contents, credentials, and private record values unless they are necessary and can be shared safely. A precise description of expected versus observed output is more useful than a large unsorted log.
Version and sources
This guide describes the Kition desktop app as of source 7d49036f, checked on 2026-11-06. Connected actions also depend on the configured model provider or service. If your installed version is older, some controls may differ.
Related pages
Test a workflow with representative sample data
A workflow test runs a configured action against a real row. It helps uncover missing fields and connection problems before the workflow is enabled.
Schedule workflows with an explicit timezone
A scheduled workflow uses a cron expression and a timezone to determine when it runs. Kition provides frequency choices, an advanced cron field, and a preview of the next runs.
Troubleshoot email connection and sending errors
Email troubleshooting separates provider authentication, transport settings, and workflow execution. Each stage can fail independently.