Timeline for Handling a combination of async callouts, schedulable jobs, and queueable jobs
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2020 at 20:25 | comment | added | identigral | It's not enough information to say what's going on. With technically complex questions such as yours, it helps to have enough code + metadata for an MVR (minimum viable reproduction). | |
| Aug 6, 2020 at 19:34 | comment | added | Douglas | I edited my post. It still sounds a little confusing, so let me know if I can clarify in any way. It does seem like I'm running into some scalability issues as @cropredy mentioned. | |
| Aug 6, 2020 at 19:20 | comment | added | identigral |
From your question: I run into the governor limit of only one queueable job being allowed to exist at a time. That is a per async transaction limit. It would apply regardless of how many Order instances are processed - one or many. Perhaps you're running into a different limit? It would be helpful to see a a specific description of the problem (including exact errors and stack traces, if any) and the code or metadata to reproduce the problem. (Please edit your post).
|
|
| Aug 6, 2020 at 18:45 | comment | added | Douglas |
If I'm understanding you correctly, I'm currently not having an issue having Services B-G run. My issue is coming up because I'm getting multiple instances of Service A spawning multiple "queued" calls to Services B-G. What I mean is that when an Order gets triggered, it calls B-G. Previously, when only one Order gets modified at a time, this was fine. But now multiple Order objects are getting modified at once.
|
|
| Aug 6, 2020 at 18:38 | history | answered | identigral | CC BY-SA 4.0 |