6 months ago
I have been getting a ton of these in the past few days:
Failed to invoke cron execution
We were unable to start your cron execution. If this error persist, please contact support.
--
It takes often 3-5 clicks to get the job to run, with a lot of waiting and these errors in between. Very frustrating.
6 Replies
6 months ago
And while some runs get going they just seem to hang at times. The ones that go through work so this is not a matter of a failing job definition.
6 months ago
Hmm, I was able to trigger a manual execution on the first try. Could you please share a screen recording of when you see this happening (preferably in a link like Loom)? Additionally, sharing your console tab in the browser in the recording?
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Had no issues for a few days, but now back at the frustrating behaviour. Don't have a recording now, but a screenshot. Will record later if needed.
Attachments
Status changed to Awaiting Railway Response Railway • 6 months ago
6 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
6 months ago
🛠️ The internal ticket Intermittent Fail to invoke cronjob has been marked as backlog.
6 months ago
I'm not able to reproduce it at this time, but I've put a ticket into our backlog. We will aggregate occurences together, and then hopefully we can figure out what's causing this over time.
Apologies I understand that's deeply frustrating. If you manage to reliably reproduce it, please let us know and we will look ASAP!
Status changed to Awaiting User Response Railway • 6 months ago
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago