Custom cmcontfinalappr flow getting Invalid action; not in state ready to activate at Landmark Node

Jeff Johnson

We have customized (repurposed) the Contract Final Approval IPA flow to go to one of 3 branches based on a different criteria then previously defined - only change.  As such, when Approver 1 rejects the contract, the flow correctly goes to the Landmark node but sits there and processes for 30 minutes before timing out and terminating abnormally.  There are 9 reject nodes in the entire flow and all have the same action out of the box (SetAction = "RejectFinalApprovalNeedsApproval").  We kept that same set action, but it is failing when it runs fine in the out of box non custom flow.  Getting the error message in the log stating "Invalid action; not in state ready to activate" which doesn't make a lot of sense since the Contract State node doesn't set anything - see below:  New criteria is in the first line and commented out line is the out of box code.  It is like the contract isn't in a state where the reject action can occur - Invalid action; not in state ready to activate, but the contract has been rejected and sent to the Landmark node where the code below happens.  Does anyone see where the issue is here?  Any help would be greatly appreciated.  Thanks.  Jeff

appsCriteria3=="PAYABLES CONTRACTS" || appsCriteria3=="LEASES"

//(!AddendumExists&& !AmendmentExists)

LANDMARK NODE:

_dataArea="<!appProdline>" & _module="po" & _objectName="Contract" & _actionName="<!SetAction>" & _actionType="CreateUpdateDelete" & _runAsUser="<!UserAction510_users[0]>" & Contract_action_comment="<!UserAction510_messages>" & Contract_reason_code="<!UserAction510_reasons>" & ContractGroup="<!ContractGroup>" & Contract="<!Contract>" & Name

Fails here in the log file:  Example below is one of a successful one.

Landmark:Landmark7030 Retrieving page 1 completed @ 10/27/2022 04:45:46.376 PM
Landmark:Landmark7030 transaction complete:true,

andy

It's possible you're attempting to invoke a state action on a record that's not in that state / state cycle. If you look at the Contract business class there are probably is a Final Approval state or Needs Approval state, or something similar and a Reject action nested under that. Can you confirm the Contract you are trying to reject is in the relevant state? Since you changed the branch condition the flow may be passing a Contract that's not in the FinalApprovalNeedsApproval state, and thus the action fails to be invoked.