In some cases, it's possible for an update to a Shopify resource to trigger an update event (e.g. "shopify/products/update"), resulting in a task run that performs a "shopify" action updating that same Shopify resource, resulting in an identical task run and an identical "shopify" action.
This infinite loop can – and should! – be prevented by the task developer, by detecting when a resource should have an update applied, and when it should not.
However, in cases when a loop does emerge, Mechanic will now step in and pause the offending actions.