meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| releases:2026-05-23 [2026/05/23 12:00] – Add BPMN interoperability section claude | releases:2026-05-23 [2026/05/23 12:10] (current) – Add Workflow Timer Node (K93) claude | ||
|---|---|---|---|
| Line 90: | Line 90: | ||
| Schema: '' | Schema: '' | ||
| + | |||
| + | ===== Workflow Timer Node ===== | ||
| + | |||
| + | New **Timer** node type in the Workflow Designer (K93). A Timer node pauses a workflow instance for a configured number of minutes and then advances it automatically - no human action required. | ||
| + | |||
| + | **Configuration: | ||
| + | |||
| + | **Runtime behaviour: | ||
| + | |||
| + | - Engine arrives at a Timer node ? inserts a '' | ||
| + | - Instance waits | ||
| + | - '' | ||
| + | - Next engine tick ? instance detects '' | ||
| + | |||
| + | No new cron job - timer firing is integrated into the existing '' | ||
| + | |||
| + | **Use cases:** follow-up reminders after a step, automatic escalation if no action is taken within a time limit, cooling-off periods between steps. | ||
| + | |||
| + | Schema: '' | ||