When enabled, scheduled runs enter a pending state and wait for manual approval. Approve via API to proceed; reject reverts pipeline to Draft status.
APPROVAL REQUIREDThis reference topic explains the approval workflow gate that can be applied to any pipeline declaration. When the `APPROVAL REQUIRED` clause is present in a `PIPELINE` block, every triggered run transitions to a `pending_approval` state instead of executing immediately. The clause takes no additional arguments; its presence alone activates the gate, and omitting it means runs proceed without human intervention. A pending run can be approved through the control plane API (`POST /pipelines/{id}/approve`), which advances it to the execution queue, or rejected (`POST /pipelines/{id}/reject`), which cancels the run and reverts the pipeline status to Draft. The approval workflow interacts with the `SCHEDULE` clause such that cron-triggered runs still honor the scheduled time but will not begin statement execution until approval is granted. If `MAX_CONCURRENT` is set on the associated schedule, pending-approval runs do not count toward the concurrency limit until they are approved and actively running.