1.6.6 Task categories and generation timing
Tasks can be categorized as follows according to the schedule type specified when the service was submitted for execution.
No. |
Task category |
Description |
---|---|---|
1 |
Immediate |
This category of task is generated when a user submits a service for immediate execution. When the service is submitted, the JP1/AO system generates a single task and executes it immediately. |
2 |
Scheduled |
This category of task is generated when a user submits a service for execution at a specified date and time. When the service is submitted, the JP1/AO system generates a single task and executes it once at the specified time. Between generation and execution, a scheduled task stays in Waiting status. |
3 |
Recurring |
This category of task is generated when a user submits a service for execution on a recurring schedule. When the service is submitted, the JP1/AO system initially generates a single task, and executes it at the specified time. As soon as the first task is executed, JP1/AO generates the next task which it executes based on the recurring schedule. This cycle of execution and generation is repeated on an ongoing basis. Between generation and execution, a recurring task stays in Waiting status. |
The following table shows when certain tasks are generated.
No. |
Service schedule type |
Generated task |
Task generation timing |
Description |
---|---|---|---|---|
1 |
Immediate |
Immediate execution task |
When service is submitted |
The task is generated when the user submits the service for execution. |
2 |
Scheduled |
Scheduled task |
||
3 |
Recurring |
Recurring task (first task) |
||
4 |
Recurring task (next task) |
When the previous task is executed |
JP1/AO generates the next task when it executes the preceding task. The cycle of executing a task and then generating the next task continues based on the recurring schedule, until canceled by a user. |