PipePilot orchestration
Schedule, run and recover pipelines.
PipePilot orchestration covers its own schedules, queues, retries, cancellation, checkpoints and recovery. It does not claim to orchestrate external ADF or Databricks jobs.
Core capabilities
Scheduling
Run batch pipelines manually, hourly, daily or weekly in an explicit timezone.
Admission
Queue work when plan, runtime or endpoint capacity cannot safely accept another run.
Recovery
Resume or retry from recorded state when the pipeline and destination make that action safe.
Execution
01Run work in the selected runtime.
Connections select a customer Private Agent or enabled PipePilot Compute. Dispatch stops when that runtime is unavailable.
One active run per batch pipeline
Persistent queue and run states
Cancellation and retry checkpoints
Capacity-aware admission where enabled
Configuration and runtime evidence stay attached to the workflow.
Dependencies
02Pipelines run independently.
PipePilot schedules and operates each pipeline independently. Cross-pipeline dependency graphs and external ADF or Databricks job control are not current capabilities.
A clear boundary for planning
No external job dependencies
Run history for operational handoffs
Dependency features require a future release
Configuration and runtime evidence stay attached to the workflow.
Next step
Plan your data workflow.
Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.