Some dependent external systems can't handle parallel message processing or requires a certain order of messages. Sending messages serially (for example, by setting the concurrency on a Logic App to 1) can be a solution, at the cost of a big performance impact.
The Invictus Framework provides a Sequence Controller component that allows you to process Logic App workflow runs in a specified order. Even parallel triggered workflows won't overblown the external dependency with messages.
See also the Message Sequence integration pattern.
Component usage
The Sequence Controller component has three main endpoints to control the sequence of Azure Logic App workflow. Use the following diagram to integrate the component in your workflow.
The component processes workflows 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 gets triggered before 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.