When several flows changed the tags of the same order at the same time, one of the flows could fail with a database error about a duplicate entry. The tags of the failed flow were then not set. This could disrupt follow-up processes that depend on these tags.

This behaviour has been changed. Changes to the tags of an order are now processed one after another instead of at the same time. This applies wherever order tags are saved, for example in flows.

Note: You do not have to change any flow. However, check the orders for which a flow ended with this error before the update. The tags step were not set for these orders. Start the flow again for these orders, or add the missing tags manually.