R1D46 Infinite Loops in Process Builder

| programming | salesforce |

Process Builder in Salesforce is a great way to do things based on some complex business logic without having to write triggers or a lot of the code yourself. As a trailblazer, I combined this with Queuable Apex that would grab the result of an HTTP POST method.

For some reason, this resulted in an infinite loop for me. I accidentally created 300+ Clubhouse tickets in a few seconds. The only way I could figure out how to stop this was to delete the opportunity record in order for the process to error out due to the opportunity no longer existing.

What I Learned

  1. More than ever, I wish that apex had feature flags. :)
  2. I have no idea how or why this happened, but the "solution" was to post the response URL to the salesforce record and then add a condition in the process builder to only run the process if the field was empty. This seems prone to failure, so we will see how things go.
I think ultimately the main issue is that I don't have a deep understanding of how asynchronous apex actually works and I am probably going about solving this problem the wrong way.

 

 

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

Doing less, for her

My daughter will be born soon, and I’m reflecting on what that means for my OpenSource work.

via Carlos Becker February 1, 2026

The Browser’s Little White Lies

So I’m making a thing and I want it to be styled different if the link’s been visited. Rather than build something myself in JavaScript, I figure I’ll just hook into the browser’s mechanism for tracking if a link’s been visited (a sensible approach, if I d…

via Jim Nielsen’s Blog February 1, 2026

$29 million stolen from from Step Finance treasury wallets

The Solana-based defi portfolio tracker Step Finance lost 261,854 SOL (~$28.7 million) when a thief gained access to treasury and fee wallets. It's not yet clear how the attacker was able to steal the funds, although Step Finance…

via Web3 is Going Just Great February 1, 2026

Generated by openring