-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[v2.0.0-alpha.6] New cron events never get generated when importing metadata #6733
Comments
I've seen the same thing in alpha.5. They'll stop running until I go in and click save, then they get recreated properly. |
Hi, we're having the same issue. A simple test case for this is:
Project with one cron cron-triggers-no-data-available.zip. A couple of things I've noticed:
Hopefully the Hasura team can chime in on this one! Thanks |
Hey Folks, I was able to repro this issue but I'm not sure if this is the entire issue. I did the following steps:
Is this all? |
I haven't experienced the cron triggers not showing up on the events page (though that may well happen). The specific problem I experienced was that the cron triggers do not execute. They also show 'no data available' instead of a list of pending events. I think this is identical to what @dariocravero sees. And it's worth noting that I also deleted and recreated the underlying database around the time I upgraded my dev machine to the Hasura 2.0 alpha. |
@rossng Can you check if there are any logs with You can also check the |
I don't see any logs coming out with that I also had a look at Then I looked at
|
@rossng Can you send me the steps to repro this issue? Also, do you see this issue in a newly created cron trigger also? |
@codingkarthik the issue isn't about the event definition showing up. It does. The problem is with the scheduled crons. If you load the event using the CLI's apply metadata/reload steps, it doesn't work. The code I shared here has the minimal steps that show the problem if you need it https://github.com/hasura/graphql-engine/files/6308780/cron-triggers-no-data-available.zip. |
I'm pretty sure my issue is identical to @dariocravero's repro. If you're not able to reproduce an issue using his example code/instructions then I can also try and put one together 🙂 |
@dariocravero @rossng Are you able to repro this issue by importing the metadata via the console instead of the CLI? |
@codingkarthik I just tried and had the same problem. Btw, I got the metadata from |
@dariocravero Can you do the following steps and let me know if the issue still persists?
|
@codingkarthik I tried and it didn't work. This time around I didn't even get the test cron on the list of possible crons. This is the metadata exported from the console: I recorded a video in case it helps: |
@dariocravero Thank you! I was able to reproduce this issue successfully. I will update here as soon as I find anything or with the fix 😄 |
amazing @codingkarthik! thanks so much 🤗 I'm around if you need anything |
closed via 72c24ee |
Hurrah! Kudos to @dariocravero for putting in the hard work to build a working repro (so that I didn't have to!). |
Thanks @codingkarthik! Would the change on dropFutureCronEventsTx also fix this #5461 (comment)? |
@dariocravero Yes, it should solve it! |
For anyone else wondering, this seems to be fixed on the latest beta |
I recently upgraded my local Hasura instance to v2.0.0-alpha.6.
I now find that Cron Triggers fail to fire most of the time. They only start to fire again once they are manually 'saved' in the Console. Until then, they just display the message 'No data available' in the Pending events tab. Here's what it looks like:
Specifically, I'm running
hasura/graphql-engine:v2.0.0-alpha.6.cli-migrations-v2
in Docker v20.10.5 on Windows 10.The text was updated successfully, but these errors were encountered: