- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] The script was executed even after the range specified in the interval setting of the schedule trigger
Search via FAQ No.
NEW
[DataSpider Servista] The script was executed even after the range specified in the interval setting of the schedule trigger
In the interval setting of the schedule trigger, I specify the time range thru [Specify time range] and select [Wait till current execution ends] under "Launch limitations ".
When the script execution time turned out longer than I expected and greatly exceeded [End Time], the following script was executed even after the [End Time].
Why was the script running even after the specified range?
- Category :
Answer
■Specification
In the interval schedule trigger, "Expected Ignition Time" to run the next script is calculated using the settings and the current time right before the script execution.
For this reason, the script may be executed even if the script takes time and it exceeds the [End Time].
*For the actual operation, please refer to "■Specific Example" below.
■Notes
If the script required time greatly exceeds the execution time range or the execution interval, it is highly possible that the script will be executed even after [End time].
Please set the execution time range and the execution interval to be longer than the script required time.
■Specific Example
We assume that the interval schedule trigger is operated with the following settings:
- Execution Interval 1 hour
- Execution Time Specify Time Range
- Start Time 09:00
- End Time 12:00
- Launch Limitations Wait till current execution ends
- Script Time Range If the processing number is 0, it will finish in one minute, but if the processing number is large, it will take up to 3 hours
If the processing number for the initial script execution is large and it takes 3 hours and the processing number is 0 for the subsequent script execution and it takes one minute, the process will be as follows.
- Before 09:00
Since the start time is 09:00, an expected ignition time will be 09:00.
- At 09:00
The script is executed because the current date and time reach the expected ignition time (09:00).
Before the script execution, the interval schedule trigger adds the execution interval (1 hour) to the expected ignition time (09:00) and updates the expected ignition time to 10:00. (Assuming it took 3 hours for the script process)
- At 12:00
The script is executed because the current date and time are already passed the expected ignition time (10:00).
Before the script execution, the interval schedule trigger adds the execution interval (1 hour) to the expected ignition time (10:00) and updates the expected ignition time to 11:00. (Assuming it took one minute to the script of processing)
- At 12:01
The script is executed because the current date and time are already passed the expected ignition time (11:00).
Before the script execution, the interval schedule trigger adds the execution interval (1 hour) to the expected ignition time (11:00) and updates the expected ignition time to 12:00. (Assuming it took one minute to the script of processing)
- At 12:02
The script is executed because the current date and time are already passed the expected ignition time (12:00).
Before the script execution, the interval schedule trigger adds the execution interval (1 hour) to the expected ignition time (12:00) and updates the expected ignition time to 13:00. (Assuming it took one minute to the script of processing)
- At 12:03
The script will not be executed because of the current date and time have not reached the expected ignition time (13:00).
Reference information
･ Help [Operational Tools]-[Trigger]-[Schedule Trigger]