Timeline for System.QueryException: Record Currently Unavailable
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14 at 13:22 | vote | accept | Thomas | ||
| May 14 at 13:21 | answer | added | Thomas | timeline score: 0 | |
| Mar 26 at 15:59 | comment | added | cropredy | Thomas -- so there is a callout involved between the SELECT FOR UPDATE and the update DML statement? | |
| Mar 26 at 10:38 | comment | added | Thomas | @cropredy Thank you. Please add this as an answer. | |
| Mar 25 at 16:59 | comment | added | cropredy |
As for Q1 - Yes, still in async context. Note that if the UpdateCounterKPIprotocol does a callout, the For Update lock is released and needs to be re-acquired. Switch the future to queueable and if you get the error, chain a new queueable
|
|
| Mar 25 at 11:24 | history | edited | RubenDG | CC BY-SA 4.0 |
Formatted code and error message
|
| Mar 25 at 10:33 | history | asked | Thomas | CC BY-SA 4.0 |