XJob runs a command on a schedule using an application’s image and relevant runtime environment. It creates an independent task container; it does not execute inside the running application container.
Create a task
- Open the application’s XJob area as an Operator or Admin.
- Give the task a recognizable name.
- Enter a command available in the image.
- Set the waiting interval after each run ends.
- Set the maximum runtime and save.
- Run or wait for an execution, then inspect status and logs.
Each application supports up to 16 tasks. Interval and execution timeout are required, each from 1 to 1440 minutes. Use an explicit shell when your command needs variable expansion, pipes, or other shell behavior.
Do not assume a job inherits writable data from a live container. Make required services and data accessible through the task’s actual configuration.
Operational design
Commands that send messages, write records, or call external APIs should handle repeated execution appropriately. Scheduling is not a transaction system for those external side effects.
A successful container exit only proves the command reported success. Make its exit status reflect the operation you intend to verify.
Verify and troubleshoot
Check the selected image, command tools, environment, target service connectivity, and execution time. Inspect the XJob log source for the specific task name.
Scheduling rules explain intervals, timeouts, and recovery. Results and troubleshooting explain last/current execution state and failures.