Runs, gates, and workflows: the primitives, explained

Upsun Dispatch defines workflows as reusable templates that specify triggers, agent actions, and optional human approval points, while runs are individual, immutable executions of those workflows for specific pull requests, issues, or scheduled events. Each run records its trigger, context, outputs, costs, and approval history, enabling execution-level auditing rather than workflow-wide estimates. Gates are deliberate stopping points within a run that require an explicit decision from an assigned human owner, such as engineering, product, or security, and workflows may contain none, one, or multiple gates depending on their purpose. The platform’s initial PR Review workflow produces an automated structured review without requiring a gate, whereas code-writing workflows commonly require approval before merging. Upsun Dispatch currently supports GitHub SaaS and self-hosted GitLab triggers and uses a user-provided model key across workflows, while automatic task-based routing among different models remains planned.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.