Timeline for Get the actual Previous Fire Time of a CronTrigger / Scheduled Apex
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2019 at 14:55 | answer | added | J. Schreiber | timeline score: 1 | |
| May 6, 2019 at 12:30 | comment | added | Brian Miller | I hear - I just don't think the current running job has any knowledge or access to the previous runtime :-/ | |
| May 6, 2019 at 7:54 | comment | added | J. Schreiber | Implementing a custom log functionality would be my last resort. I have a logging / disagnostics package in place which I could utilize. But I prefer native platform functionalities ober custom "hacks" (because ihey always introduce new dependencies, which I prefer to avoid). | |
| May 5, 2019 at 12:15 | comment | added | Brian Miller |
Have you tried saving previous CronTrigger Ids and querying them after more than one job has run? For sure it's not ideal, but you could create your own CronTrigger_Log__c custom object and in the finish() method (or even start()), create a new log record with an Id to the previous run, as well as run times.
|
|
| May 5, 2019 at 7:03 | history | asked | J. Schreiber | CC BY-SA 4.0 |