Running Workflows Manually
How to trigger workflows from the Borker UI and read the workflow history log.
You can trigger any workflow manually from the Borker dashboard. No cron setup needed to get started.
Triggering a workflow
Navigate to the Workflows section in the main nav.
Find the workflow you want to run (Daily, Weekly, or Process Approved).
Click Run to trigger it.
The workflow card shows a spinner and "Running..." state. A Cancel button appears.
When complete, the card updates with the result: how many items were generated or scheduled, and any errors.
The running state
While a workflow is running:
- The Run button is replaced by a Cancel button
- The workflow card shows a live progress indicator
- You can navigate away; the workflow continues in the background
- Only one workflow can run at a time
Clicking Cancel stops the workflow mid-run. Any content already generated in that run is preserved (it won't be deleted). Cancellation takes effect after the current slot finishes processing.
Don't run the same workflow twice in quick succession. If the daily workflow is still running, starting it again will be blocked.
Workflow history
Every workflow run is logged. Access the history from the Workflows page → History tab.
Each log entry shows:
- Workflow type (daily / weekly / process-approved)
- Run time and duration
- Status:
completed,failed, orcancelled - Summary: items generated, items scheduled, errors
Workflow run detail view
Click any history entry to open the detail view.
The detail view shows:
- Per-slot breakdown: for daily runs, one row per calendar slot
- Topic selected: which topic the Decision Engine chose and from which pool
- Generation status: success, failed (with error message), or skipped
- Content item link: click through to the generated content in the approval queue
The detail view is your primary debugging tool. If a slot failed to generate, the error from the Claude API (e.g., "rate limit exceeded" or "context length error") is shown here.