'Due Date' functionality on 'Ask for Approval action' Flow action is setting the approval records to 'No Longer Required'. Issue When "Due Date" in the "Ask for approval" action of the flow is used and a condition is specified like: Reject if pending by X number of days (or) Cancel if pending by X number of days and if the "Due Date" is reached, the flow does not automatically mark the approval record as "Rejected" or "Cancelled". Instead: The 'State' of associated Approval Record(s) is marked as: "No longer required" ReleaseAll ReleasesCauseThis is by design and expected behaviour. The approval records are expected to to be marked as 'No longer required' as the flow has taken the action at RITM level i.e the approval field on RITM has been marked as 'Rejected/Cancelled' (as specified in the 'Ask for approval' action). As the flow is attached to RITM - and once the 'Approval State' which is the outcome of 'Ask for Approval' action is marked as 'Cancelled/Rejected' the 'Approval field' on the RITM gets marked as cancelled. This indicates that no human action was taken, and the system bypassed the request.ResolutionWhen the "Due Date" is reached and the condition (e.g., Reject if pending by X days) is triggered: - The approval action will be marked 'completed' automatically in the flow context. - The approval record's state becomes "No longer required". No actual state (like "Rejected" or "Cancelled") is assigned, because no approver explicitly took that action. This allows downstream logic to treat bypassed approvals differently from manual decisions — giving user the flexibility to handle them as needed.Related LinksAsk for approval action product documentation: https://www.servicenow.com/docs/bundle/yokohama-build-workflows/page/administer/flow-designer/reference/ask-approval-flow-designer.html