After recovery from quick startup, MEAP applications do not work properly.
MEAP applications that are scheduled to execute processes at specified times may not work properly after recovery from quick restart.
Unexpected problems such as that the application executes a task at an unexpected timing may occur.
Problems may occur in the following two cases.
In the case of "Schedule: Execute the task every 24 hours"
A schedule is set to start the specified task at the specified time and repeat "fixed-delay execution".
If execution is delayed for some reason, the delay time is ignored.
Problem: If 24 hours have passed since the last execution of the task, the task is executed only once.
=> The task may be executed at a timing other than the time the user expects it to be executed.
In the case of "Schedule: Execute the task at 00:00 every day"
A schedule is set to start the specified task at the specified time and repeat "fixed-rate execution".
If execution was delayed for some reason, two or more tasks are continuously executed to "make up for the delay".
Problem: The tasks of Jan. 1, Jan. 2, and Jan. 3 are executed after quick startup.