Timeline for APEX Scheduler Queue Confirmation
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2018 at 19:14 | comment | added | Olivia | I appreciate your feedback on the initial question, I know this thread got a little overly complex. We can't use a trigger for a number of reasons that are too much to lay out in this thread. I wasn't in need of architecture help, so your feedback on the scheduler code was great. Thank you! | |
| Feb 20, 2018 at 18:15 | comment | added | Adrian Larson♦ | @Olivia Perhaps try laying out your goals at a higher level. It's not really clear why you want to implement Flow, Platform Events, webservice, or any of the technology stack you mention above. If your stack is this complex, you probably should be paying someone to assist. Free help is likely not going to cut it, and the format here is to constrained for the breadth of conversation you need to carry out. | |
| Feb 20, 2018 at 17:54 | comment | added | Olivia |
I updated the post with why we can't use a trigger instead of a scheduler. Where would you suggest I use a trigger? The incoming third party and the webservice callout is counting as two rest services which is creating the Callout loop not allowed error. I believe I have to split the transactions apart so there is no "loop"
|
|
| Feb 19, 2018 at 22:59 | history | edited | Adrian Larson♦ | CC BY-SA 3.0 |
added 668 characters in body
|
| Feb 19, 2018 at 22:53 | history | answered | Adrian Larson♦ | CC BY-SA 3.0 |