-
Notifications
You must be signed in to change notification settings - Fork 31
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
Updating alarms feed params does not change scheduled trigger execution #205
Comments
Thanks for raising this up @duynguyen ! |
@meryllblanchet , yes that's possible. We might need some inspection in the alarms provider at Runtime level. |
This only affects the "alarms related params", e.g. |
Thanks for the update @duynguyen . Can you reproduce it using |
this does works with the |
In the manifest.yml file, you can specify schedule cron jobs with trigger feeds and rules.
After that you might want to update the interval to be 3 minutes instead of 1. Then
aio app deploy
. After redeployed you can check the info ofsync-users
trigger. It shows 3 minutes correctly.However the trigger is still fired every minute, like it was never updated.
This could be an issue with the alarms package itself, but creating this ticket for triaging purpose.
The text was updated successfully, but these errors were encountered: