azure-webjobs-sdk-extensions icon indicating copy to clipboard operation
azure-webjobs-sdk-extensions copied to clipboard

Consistently set IsPastDue for all invocations

Open mathewc opened this issue 5 years ago • 2 comments

Currently IsPastDue is only computed/set on startup on startup time invocations.

For non-startup time invocations, we compute the Next scheduled invocation from the current invocation start time. If the current invocation runs long (past that next scheduled occurrence), the function is behind schedule and will be invoked immediately (code here). However IsPastDue remains false here.

User code can always determine if the current invocation is past due in these cases, by checking if ScheduleStatus.Next – now is negative past a threshold they define (e.g. if Next is 12:00 but its 12:01 now, we’re a minute overdue). However, I think we should consistently set IsPastDue.

mathewc avatar Feb 21 '20 20:02 mathewc

Hi @mathewc , Do we have any further updates here, request you to tag the issue to the right label if there is no necessity of triaging

v-anvari avatar Dec 07 '20 11:12 v-anvari

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

ghost avatar Dec 12 '20 18:12 ghost