Replies: 6 comments 1 reply
-
Hmm, have you looked at the actual job row being produced by this insert? For a working example, I would expect its state to be Normally we see the scheduled time set via the insert opts as part of the insert function call, but I believe the method you’re doing (pulling it from args via |
Beta Was this translation helpful? Give feedback.
-
I've checked the job row, and it seems like the job isn't being attempt at all. I scheduled the job for a minute later, but it hasn't run at all. I've even tried larger intervals but to no avail |
Beta Was this translation helpful? Give feedback.
-
@Ayo-Awe One thing I don't see in any of your sample code is a call to |
Beta Was this translation helpful? Give feedback.
-
My bad, I actually called start but I forgot to include it in the sample code The weird part is that it's only scheduled tasks that don't run, regular tasks run fine |
Beta Was this translation helpful? Give feedback.
-
@Ayo-Awe Try running River with a debug-level logger. You should be able to look for log lines that start with "JobScheduler" which should give a hint as to what's going on. |
Beta Was this translation helpful? Give feedback.
-
@brandur I just checked the debug logs and I can't find anything on the scheduler. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to schedule jobs for a later date with riverqueue, but it doesn't seem to be working. If I take off the ScheduledAt insert option everything seems to work fine otherwise, it doesn't work.
Here's my setup
Beta Was this translation helpful? Give feedback.
All reactions