Suspending a pipeline used to be a psql-only operation.
Pipeline Ops Controls
One operator cockpit lets you suspend, prioritise, chain, and bulk-action pipelines without leaving the list.
Operate
Incident response shouldn't take four pages and a dozen context switches. Pipeline Ops Controls collapse priority, suspend, auto-restart, schedule edit, and parent-child chaining into one drawer and one bulk bar on the pipelines list.
What it solves
Common problems this capability removes from your engineering workflow.
Reordering run-pickup priority lived in a separate page.
Bulk pause and resume across ten pipelines took ten clicks each.
Auto-restart on failure required custom orchestration code.
How it works
The flow this capability runs end-to-end inside the platform.
- 1Every row shows priority, watchdog state, suspended flag at a glance.
- 2Click a row to open the full settings drawer for that pipeline.
- 3Check multiple rows for a bulk bar that writes the same patch shape.
- 4Chain one pipeline to trigger another — cycles are detected for you.
Related capabilities
Other capabilities in the BoltPipeline platform that work alongside this one.
4Self-Healing Runtime
Operations Monitor
One sidebar item answers every on-call question — what's running, what failed, what drifted, what to fix first.
4Self-Healing RuntimeOperate Orchestrator
Pipeline steps run in true parallel with dedicated connections, classified errors, and policy-driven retry.
4Self-Healing RuntimeTasks and Pools
Every job runs in a credential-isolated pool — slow profiles never block urgent loads, and the agent decides its own capacity.
See it on your data.
Try BoltPipeline against your live database — your data never leaves your environment.