1

I am trying to diagnose this error when my timer function runs. I have not found much help on this on google search

UnscheduledInvocationReason: IsPastDue, OriginalSchedule: 2019-06-13T15:13:00.0000000-07:00

It seems like the process just stops when this error comes.

Anyone have any insight on this?

Sarah
  • 1,199
  • 2
  • 21
  • 42
  • IsPastDue is a flag set when the timer is overdue, as Haitham Shaddad's answer below describes. It shouldn't halt further timer executions, though. Could you post your issue to the Functions GitHub for tracking and provide the following information for the product team to investigate: timeframe, function app name, function name(s), region, invocation ID(s). Thanks! – Katy Shimizu Jun 14 '19 at 21:00
  • I know this is old but I had a similar issue and found out that I was on free plan which stops keeping your function app "alive" hence the timer function will not execute. I have to access it via azure and then magically my timer functions execute. – snowflakes74 Jul 22 '20 at 00:01
  • Does anyone know if this error happens if the timertrigger previous run exceeds the timeout? – Joe Eng Jun 28 '21 at 19:00

2 Answers2

1

The IsPastDue flag is passed to your azure function to indicate if the timer was overdue or not. A timer function can run late in some scenarios like the app service was restarted, in this case it is still invoked but the IsPastDue flag will be set to true to give your function a chance to react.

These links are helpful

Timer trigger for Azure Functions

Also, it seems that it was an issue and it is submitted on github but that was on 2017

TimerTrigger can miss IsPastDue

Haitham Shaddad
  • 4,336
  • 2
  • 14
  • 19
1

Got this error locally.

enter image description here

[2021-06-16T14:58:22.779Z] Executing 'Functions.TimerTrigger' (Reason='Timer fired at 2021-06-16T16:58:22.7688953+02:00', Id=adbaee54-8a3e-4983-a7e4-a73f69153e5e) [2021-06-16T14:58:22.780Z] Trigger Details: UnscheduledInvocationReason: IsPastDue, OriginalSchedule: 2021-06-16T16:37:00.0000000+02:00 [2021-06-16T14:59:22.614Z] Starting worker process failed [2021-06-16T14:59:22.615Z] The operation has timed out.

Solved by clearing Blob Emulator locally:

delete
  FROM [AzureStorageEmulatorDb510].[dbo].[Blob]

enter image description here

Ogglas
  • 62,132
  • 37
  • 328
  • 418
  • My storage is in azure, I cleaned the `azure-webjobs-hosts` container and restarted. Got a bunch of errors, re-restared and voilà it works. Thanks! – Maxime Morin Jul 21 '21 at 16:05