Timeline for Does Queueable Apex guarantee preventing deadlocks if implemented correctly?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2023 at 0:44 | history | became hot network question | |||
| Mar 6, 2023 at 17:53 | answer | added | sfdcfox♦ | timeline score: 5 | |
| Mar 6, 2023 at 17:15 | answer | added | Phil W | timeline score: 1 | |
| Mar 6, 2023 at 16:57 | comment | added | identigral | No, it wouldn't. You need an explicit solution in your architecture that considers the possibility and/or prevents the deadlock This could be custom code, existing code that strings components and/or calls together in some way, automation that is not code, data model changes, etc. | |
| Mar 6, 2023 at 16:52 | answer | added | Renato Oliveira | timeline score: 3 | |
| Mar 6, 2023 at 16:38 | history | asked | Chris | CC BY-SA 4.0 |