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

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”.