Reset Flow Limits with Pause Element

1 Reply

Has anyone tried this? Has it worked for you?

Yumi Ibrahimzade’s “Salesforce Time” blog floated a fascinating idea:

adding a zero-duration Pause Element to an Autolaunched Flow.

“By doing so,” Yumi writes, “this element will end the flow transaction, which will reset the flow limits.”

configuring that would look like this:

. . . I imagine this easily fixes a Flow that’s running into limit errors.

On the flip side, I could imagine this superficially fixing a Flow without addressing underlying problems.

I’d love to hear your experience! I hope to update this post after I get a chance to test.

1 thought on “Reset Flow Limits with Pause Element”

  1. Ezra Kenigsberg's avatarEzra Kenigsberg Post author

    Well-Architected Salesforce isn’t a fan of zero-minute pauses. From their page on Record-Triggered Automation:

    The other “hack” that has been used was to add a Pause element using an autolaunched subflow that waited for zero minutes, and then call that flow from Process Builder. That “zero-wait pause” will effectively break the transaction and schedule the remaining automation to run in its own transaction, but the mechanisms it uses do not scale well, as they were not designed for this purpose. As a result, increased use will lead to performance problems and flow interview limits. Additionally, the flow becomes more brittle and difficult to debug. Customers who have used this approach have often had to abandon it after reaching scale. We do not recommend starting down that path (pun intended), which is why it’s not available for subflows called from record-triggered flows.

    (emphasis added.)

    Reply ↓

Leave a reply to Ezra Kenigsberg Cancel reply