1.6.11 Task categories and generation timing
Tasks can be categorized as follows according to the execution timing specified when the task was submitted for execution.
No. |
Task category |
Description |
---|---|---|
1 |
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 |
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 |
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 the timing with which tasks are generated.
No. |
Service execution timing |
Generated task |
Task generation timing |
Description |
---|---|---|---|---|
1 |
Immediate execution |
When the service is submitted |
The task is generated when the user submits the service for execution. |
|
2 |
Scheduled execution |
|||
3 |
Recurring execution (First task) |
|||
4 |
Recurring execution (Next task) |
When the task is executed |
JP1/AO generates the next task when it executes the first task. The cycle of executing a task and then generating the next task continues based on the recurring schedule, until canceled by a user. |