New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timer tigger fails to fire #336

Closed
LoungeFlyZ opened this Issue May 5, 2016 · 7 comments

Comments

Projects
None yet
2 participants
@LoungeFlyZ

LoungeFlyZ commented May 5, 2016

I have a C# function triggered every 30 mins. However from time to time it stops firing. When that happens I log into the Azure portal, go open that function and magically it springs back to life and the trigger fires again. Its like its being woken up when I go in there.

I sadly have no solid repro i'm sorry.

@davidebbo

This comment has been minimized.

Contributor

davidebbo commented May 5, 2016

Is your function running in a Dynamic plan or Classic plan? If classic, make sure it is Basic or Standard, and has Always On turned on.

Also, can you share your function app name, either directly or indirectly? This will help us investigate.

One more thing: the approximate time where you saw this happen could help track it down.

@LoungeFlyZ

This comment has been minimized.

LoungeFlyZ commented May 5, 2016

We have it in an S1 plan. Not sure how to tell if Classic or Dynamic? Must be dynamic as we don't have the Always On toggle.

@davidebbo

This comment has been minimized.

Contributor

davidebbo commented May 5, 2016

S1 is actually Classic. To check the Always On toggle:

  • Functions app settings / Go to App Service Settings
  • Settings / Application Settings
  • Look for Always On
@LoungeFlyZ

This comment has been minimized.

LoungeFlyZ commented May 5, 2016

Ah right! Thanks! Probably would be useful for that to be on by default no?

@davidebbo

This comment has been minimized.

Contributor

davidebbo commented May 5, 2016

Yes, it really should be. You created the Function App using the Azure Portal, right?

@davidebbo

This comment has been minimized.

Contributor

davidebbo commented May 5, 2016

I confirmed that creating a new S1 Function app does not auto set the Always On bit. Definitely a bug which we'll fix. I'll close this issue since that logic lives in the Azure portal which is not on GitHub.

Thanks for reporting!

@davidebbo davidebbo closed this May 5, 2016

@LoungeFlyZ

This comment has been minimized.

LoungeFlyZ commented May 5, 2016

Thanks for the assistance! Yep, created via portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment