Cannot debug in VS 2019 when TimerTrigger invokes due to IsPastDue UnscheduledInvocationReason
DavidGodbold opened this issue · 3 comments
I ran the debugger by pressing Debug in VS and also alternatively followed the guidance at here to debug locally.
On both occasions I receive the same timeout error when a TimerTrigger is invoked due to a CRON expression (see TimerTrigger C# declaration in image below) which means it runs to catch up on a missed invocation.
If I just run the functions using func host start command then the trigger runs successfully.
See image below for error messages when running Functions from CLI.
My version of VS 2019 is as follows.
I have since deployed application to Azure (Windows, Consumption plan) and it even fails there. Any timer trigger times out after 5 minutes.
If I create a new Function project using latest version of VS 2019 at time of writing (16.10.1) with a TimerTrigger using the VS template, with a CRON expression of 0 */10 * * * *, I get the same issue so I feel that rules out the issue being within my codebase.
Thanks @DavidGodbold! Tracking these debugging timeout issues in #434.