Automation schedules
Scheduled operational actions using a dedicated credential.
Dedicated credential
Scheduled operations use a separate encrypted SSH Automation credential rather than a user's personal session credential.
Schedule lifecycle
The Automation API supports create, update, delete and explicit run-now for schedules. Available actions are exposed through the automation action catalog and remain subject to safeguards.
Timezone
The global Platform timezone controls displayed historical times and provides the default for newly created schedules. Existing schedules keep their configured timezone when the Platform timezone changes.
Runbooks
A Runbook must be approved and have scheduled execution enabled before it can run unattended.
What a schedule actually creates
Automation owns why and when work runs; Jobs remains the execution record. When a schedule is due, Portivo resolves its Site, Group or explicit target scope, validates the action policy and creates a normal Job with per-target items. The scheduler does not bypass preview rules, safeguards, device serialization or audit history.
Credentials and failure boundaries
Scheduled work uses the dedicated encrypted Automation credential. Manual operations continue to use the signed-in user's personal SSH session. A missing, invalid or unauthorized service credential fails the scheduled execution without falling back to a user's session.
Operator checks
- Confirm timezone and next-run time.
- Keep target scope narrower than the action's configured maximum.
- Review the resulting Job rather than treating a triggered schedule as proof of success.
- Disable obsolete schedules instead of leaving credentials attached to unused work.