Retry application message - fails to be scheduled due to "Next execution date must be between start date and stop date"

Question

When an application messages addresses gets fail status, the framework has a mechanism to create a “one-time scheduled task” to re-execute the same message/address within a short time. At my customer environment, this sometimes fails. It is not the actual “Retry application message” that is the problem. The problem as I understands it, is the logic that catches the exception of the application message and then fails to add the “one-time scheduled task”. The error is shown on the application message with the error text “Next execution date must be between start date and stop date”. The reason to this error is that when the scheduled task is to be created, the logic fails to calculate a correct execution date. There is an logic checking that the execution date must be between

Code if from Batch_Schedule_API.Insert___

-- Check date intervals
IF newrec_.next_execution_date IS NOT NULL THEN
   IF newrec_.next_execution_date NOT BETWEEN nvl(newrec_.start_date, newrec_.next_execution_date - 1) AND
                                                    nvl(newrec_.stop_date,  newrec_.next_execution_date + 1) THEN
      Error_SYS.Record_General('BatchSchedule', 'NEXTINTERR: Next execution date must be between start date and stop date.');
   END IF;
END IF;

So, the execution date suggested is not valid for this new task and that is why the error is raised.

My questions here are: Have anyone run into the same problem? And what can possibly be done to make this work? At the moment we don’t get any “Retry application message” and the “real” error is hidden behind the raised error “Next execution date must be between start date and stop date”.

ashen_malaka_ranasinghe · Answer

Hi ​@Frbese,It sounds like the issue is not with the Retry Application Message functionality itself, but rather with the framework's attempt to create the temporary one-time scheduled task that performs the retry. The error"Next execution date must be between start date and stop date" is raised from the validation in Batch_Schedule_API.Insert___ when the calculated next_execution_date falls outside the valid schedule window.Since the problem occurs intermittently, I would investigate how the retry task's Start Date, Stop Date, and Next Execution Date are being calculated at the time the application message fails. If the generated retry execution time falls outside the allowed date interval, the schedule creation will fail and prevent the automatic retry from being created. This could be caused by timing issues, date calculation issues, or inconsistencies between application server and database timestamps.Another challenge is that the scheduling error appears to mask the original application message error. Instead of seeing the actual reason why the application message failed, the user only sees the schedule validation error. Therefore, it would be worthwhile to review the application server logs, connect logs, and database trace information around the time of the failure to identify the original exception that triggered the retry mechanism.I am not aware of a general configuration workaround for this behavior. My recommendation would be to collect evidence from a failing example, including the Application Message ID, IFS Cloud version/SU level, complete error details, and any available schedule information, and then raise a support case for further investigation. Based on the symptoms, the most likely cause is that the retry framework occasionally generates an invalid execution date for the one-time scheduled task, causing the retry creation to fail and hiding the original application message error.

Did you find what you're looking for? If not:

Sign up

Login to the community