> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planasonix.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Orchestration overview
> Schedule, trigger, and chain pipeline executions.
Orchestration controls **when** and **how** pipelines run. You move from manual execution to repeatable operations by attaching schedules, file or cloud event triggers, signed webhooks, and dependencies between pipelines.
## Building blocks
Run pipelines on cron expressions with explicit time zones.
Start runs when objects land in S3, GCS, Azure Blob, or related event feeds.
Invoke pipelines from external systems over HTTPS with optional signatures.
Model multi-step workflows with trigger nodes and dependencies.
## Design principles
* **Idempotency**: Assume retries. Design loads so a second run does not corrupt facts (merge keys, dedupe stages).
* **SLA clarity**: Match schedule cadence to business deadlines; faster is not always better if cost or contention rises.
* **Blast radius**: Isolate experimental pipelines on separate triggers so a noisy upstream does not block critical loads.
## Permissions
Creating or editing orchestration rules requires roles that can **execute** the target pipeline and **read** the connections those pipelines use. Service principals used for cloud triggers need least-privilege policies on bucket notifications or queue subscriptions.
Orchestration metadata (who triggered a run, from which webhook or schedule) appears in run history for audit.
## Next steps
Pick schedule vs event vs webhook based on how upstream systems signal readiness.
Execute manual test runs, then attach automation once outputs stabilize.
Wire [alerts](/observability/alerts) for failures and duration anomalies.