Browse and search documentation
Jobs scripts and templates
Reuse reviewed script versions, confirm parameters and targets, control batch execution and inspect per-host results.
On this page
Definitions versions and executions
A script or template is reusable job content. A published version fixes the content and parameter contract used for a task. A job definition describes targets and policy; each execution has a separate record. Editing a draft does not change a task that already ran.
Use the names, types and bounds declared by the selected version. Ordinary parameters must not contain passwords, private keys or tokens, or be used to inject unreviewed commands.
Run a job
Before starting, have an administrator confirm remote-job execution, Agent gateway security and target authorization are ready. All-in-One installation does not automatically enable remote-job execution, and an online Agent does not by itself authorize dispatch. Resolve missing configuration rather than bypassing security settings.
- Choose a script or template in the job center and review its version, supported environment and parameters.
- Confirm targets belong to the intended project and their Agents are online. Test one authorized host before a first large production run.
- Set parameters, timeout and execution policy, review targets and submit. Follow required approval or MFA for that request; do not change targets and reuse old authorization.
- Inspect each host’s status, failure summary and authorized output in the execution record.
- After completion, verify the intended operational result. For inspections, read check findings as well as execution status.
Choose batch controls
| Setting | Purpose |
|---|---|
| Maximum concurrency | Limit simultaneously executing targets to manage platform and host load |
| Batch size | Progress through targets in groups so results can be observed at a smaller scale |
| Failure-rate threshold | Combine with the minimum completed sample to decide when to stop expanding the run |
| Timeout | Bound execution time; a timeout still requires checking actual target state |
Retry failures
Find the specific failed or timed-out targets and inspect summaries and output. Determine whether the action partly took effect. Resolve service, network, access or parameter issues before using the available retry operation.
A retry creates a new execution and rechecks current access, policy and approval. Do not rerun a potentially non-idempotent script against all targets when the original result is unknown.
Reuse sequential flows
A flow template reuses reviewed steps. A new instance still requires exact targets and permitted parameter changes, without copying previous executions or approvals. Current sequential flows require step-by-step confirmation rather than acting as a general automatic orchestration or compensation engine.
Send your deployment version, page and a redacted description so we can investigate and update the guide.
weiwendi@aiops.red