At the time of writing, Azure does not provide a built-in way to control the order in which Azure Logic Apps workflow runs are processed. This can be a problem when handling entity updates, where older updates may overwrite newer ones if they are processed later. In these situations, you may want an earlier-triggered workflow to wait for a later one to complete.
Time Sequencer is a Framework component that allows you by interacting with HTTP endpoints to set up sequences, controlled by custom timestamps, to ensure that workflows run in a time-controlled fashion.
Component usage
The Time Sequencer component has two main endpoints to control the sequence of Azure Logic App workflow runs. Use the following diagram to integrate the component in your workflow.
Based on the result of the first endpoint (Start or Stop), the run should terminate or do the necessary time-sensitive actions before completing the sequence with the second endpoint.
Workflows process in sequence after the Wait. The place between the Wait and Complete task allows you to place your own logic that needs to run in order. If workflow 1 uses a custom timestamp that happened 'earlier' than the one used in workflow 2, the second workflow waits for the first workflow.
Related Bicep template parameters
Use arrow keys to navigate rows. Press Enter or Space to expand a row with sub-properties. Press / to focus the search field.