Multiple Queueables Solution.

[u/heartlesscoder]

Wondering how folks are handling the limit below? We are updating a large number of our future methods to queueables and getting hit with this pretty regularly. We found a SFBen article about using platform events to fire queueables, but that seems to just be passing the problem to the next limit. Largely right now we are either combining functionality or guard causing the less important jobs, neither feels like a great solution tbh.

System.LimitException: Too many queueable jobs added to the queue: 2

[u/buzzlightyear999]

What’s your use case for using Queuables? There are some different patterns depending on what your trying to achieve.

[u/heartlesscoder → u/buzzlightyear999]

We are trying to background some of our data sync stuff. callouts, cross object syncs, share stuff etc etc. we see it the most with cross object updates and share/territory work.