Are there any updates related to flow action execution order after upgrading Xanadu?

[xingrui]

Hi all, I'm having a problem after upgrading to Xanadu, here are the steps to reproduce:

1. Related the Schedule Entry (cmn_schedule_span) table with the Approval (sysapproval_approver) table

Note: I added a reference field to the Approval to point to the Schedule Span

2. Create a flow via Flow designer:

Record Trigger:

Schedule Entry Created or Updated.

Actions:

①:Ask for approval

①→②: If Approve State is Approved

              then Update Schedule Entry Record(Update Record Action)

3. When I do the test, the activity display field of Approval changes as follows:

When a Schedule Entry is created, an Approval record is generated.

When the Approval record is approved, the Schedule Entry is successfully updated as expected.

However, at the same time, the Approval record is back to the requested state.

After investigation, it was found that if a Pause operation is added before the Update Schedule Entry Record, the Approval record will not be back to the requested state.

So does anyone know the reason for this issue? We didn't have this problem at the WashingtonDC version before.

Any somehow updating the flow execution order behind the scenes in the Xanadu version?

Best regards

[Mark Manders · Accepted solution]

The flow engine updated from version 1 to version 2. 

Version 2 handles some things stricter than version 1 did. Don't ask me the technical details, but we had flows ending in error all of a sudden, because one step was previously just skipped because of a typo and in version 2 it errored because it couldn't find the record because of the typo.

You can check it this is the cause by moving back to version 1 on DEV and check if it is all running as before. It is handled through system property 'com.glide.hub.flow_engine.engine_major_version'. You can probably only change it through a background script.
I do not advice to move the version back on PROD, but doing on DEV will at least give you the answer if this really is the issue. If it is, you will just have to update and test your flow (back on version 2) to get it working correctly (you seem to already know the solution, so that won't be a hard thing to do).

[xingrui]

Thank you @Mark Manders ! That's very helpful.