Skip to content
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

Azure Function timer trigger not firing #1445

Closed
onionhammer opened this issue Apr 21, 2017 · 6 comments
Closed

Azure Function timer trigger not firing #1445

onionhammer opened this issue Apr 21, 2017 · 6 comments
Assignees
Milestone

Comments

@onionhammer
Copy link

Please provide a succinct description of the issue.
Similar to #740, the azure function in question is in the same resource group as dummy124441.azurewebsites.net

The timer is set to run on this schedule ( 0 */15 * * * * ), every 15 minutes, but the last time it ran according to the invocation log is (2017-04-19T14:30:0 ...)

Expected behavior

I would expect the function to run every 15 minutes

Actual behavior

The function does not run unless I trigger it manually

@paoliniluis
Copy link

paoliniluis commented Apr 21, 2017

having the same issue here, although I have it schedule for everyday at a certain hour it will never fire.
function.json:

{
"bindings": [
{
"name": "myTimer",
"type": "timerTrigger",
"direction": "in",
"schedule": "0 0 10 * * *"
}
],
"disabled": false
}

my function:

module.exports = function (context, myTimer) {
promises...promises...promises...
context.done();
};

@davidebbo
Copy link
Contributor

@paoliniluis you may be running into a different issue (discussed here). Where the function does execute, but the Monitor UI doesn't show the invocations. Please see that thread for workaround.

@onionhammer
Copy link
Author

@davidebbo yes, it looks like the same issue. I do see that it's being invoked, just not appearing in the invocation log in azure anymore

@paulbatum paulbatum modified the milestones: April 2017, May 2017 May 1, 2017
@karandesai28
Copy link

Facing same issue, Function does not execute unless I open the function in portal. I am using consumption plan, and by that I think there is no need for Always On as the system should take care of waking up my functions whenever they need to run.

@davidebbo
Copy link
Contributor

@karandesai28 please provide the app name and UTC time when you expected it to fire and it didn't.

@davidebbo
Copy link
Contributor

@karandesai28 actually, please open a separate issue. The two cases in here were actually just the monitoring issue (long fixed), and the functions were in fact getting invoked. So closing this one.

maiqbal11 pushed a commit that referenced this issue Nov 1, 2019
maiqbal11 pushed a commit that referenced this issue Nov 1, 2019
* Minor typo in error (#1445)

* Don't make unknown worker runtime a fatal error

Closes #1445
@Azure Azure locked as resolved and limited conversation to collaborators Jan 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants