Why Movement request is in delayed status as soon as it is created in 25 A?

Summary:

In 25 A, all movement requests are going to Delayed status as soon as it is generated from min-max/created manually. How to fix this issue as we don't want to see the movement requests in delayed status even if they are fulfilled on time.

Content (please ensure you mask any confidential information):

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):