Backflush Failure When WO Date Matches Component Effective Date

Summary:

Has anyone encountered an issue in Work Execution during Work Order creation where the component is not included when the transaction date coincides with the effective date change in the Work Definition?
Here’s the scenario:

• A component has a Work Definition that remains effective until a specific date and time.
• A new Work Definition for the same component, with an updated yield factor, becomes effective immediately after that date.
• A Work Order is created with a transaction date that falls exactly at the boundary between these two effective periods.

Expected behavior: The Work Order should include the component with the new yield factor.