Currently, the CRON
scheduled event contains the following properties:
cron- the CRON expression
type- always equal to
scheduledTime- the time in miliseconds
As CRONs are often used to fetch some external data, they might be a subject to a flood of new data if they run for the very first time, for example: a deployment to a new environment that needs to catch up with all the data. When looking at the dashboard, triggers, one can see the list of recent runs that is obtained using GraphQL. At the same time CRON cannot measure its execution internally, as it’s a subject to the sandboxing security mechanism, which sets the date as const for any given execution.
It would be great if the
scheduled event contained the last run time. It would allow to create adaptive CRONs that understood how long they were running without breaching the sanbox. Would it be possible to have it added dear CF team?