You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Up until recently, it was being run consistently. Starting on September 29th, however, the timer no longer triggers the function.
I can find no logs specifically pertaining to the timer attempting to fire and failing, or to the function running and failing. It just appears that nothing happens at the appointed hour.
Troubleshooting Steps Attempted
Manually running the process through the Portal is generally successful, although it did at one point produce a SocketException very similar to the ones mentioned below.
By rebooting the function and setting the schedule to run every few minutes, I was able to make it run again, but this was only temporary. After resetting the schedule to its normal 24-hour period, the timer again began failing to fire.
I also attempted the workaround mentioned in this issue by setting the WEBSITE_USE_PLACEHOLDER value to 0 and restarting the function. This appears to have had no effect.
Related information
We have a number of other Functions that run on a schedule within that app service plan, all of which have been functioning normally and firing regularly.
One of them (but only one) appears to record the same kind of SocketException errors mentioned below.
The same day that the function stopped running regularly, it began frequently logging SocketException errors at seemingly random times. Almost all of them occurred while the function was not executing.
From the appearance of the stack trace, they seem to have come from within the hosting environment: System.Net.Sockets.SocketException at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
This issue is resolved. The cause was that this function was hosted on the same server instance as another function, which had begun attempting to open ~10,000 outgoing TCP connections every hour.
Investigative information
I have an Azure Function (identifying details below) that is configured to run on a timer, according to a cron set in the environment.
The cron is
0 0 6 * * *
.Expected Behavior
The process will run at 0600 UTC every morning.
Actual Behavior
Up until recently, it was being run consistently. Starting on September 29th, however, the timer no longer triggers the function.
I can find no logs specifically pertaining to the timer attempting to fire and failing, or to the function running and failing. It just appears that nothing happens at the appointed hour.
Troubleshooting Steps Attempted
Manually running the process through the Portal is generally successful, although it did at one point produce a
SocketException
very similar to the ones mentioned below.By rebooting the function and setting the schedule to run every few minutes, I was able to make it run again, but this was only temporary. After resetting the schedule to its normal 24-hour period, the timer again began failing to fire.
I also attempted the workaround mentioned in this issue by setting the
WEBSITE_USE_PLACEHOLDER
value to 0 and restarting the function. This appears to have had no effect.Related information
We have a number of other Functions that run on a schedule within that app service plan, all of which have been functioning normally and firing regularly.
One of them (but only one) appears to record the same kind of
SocketException
errors mentioned below.The same day that the function stopped running regularly, it began frequently logging
SocketException
errors at seemingly random times. Almost all of them occurred while the function was not executing.From the appearance of the stack trace, they seem to have come from within the hosting environment:
System.Net.Sockets.SocketException at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
The text was updated successfully, but these errors were encountered: