Hi Kesava,
It's just a guess, I assume that the cron entry in question was
supposed to run on "dynamic" backend instance.
If that's the case, the cron execution can be a single point of
failure, because the cron never retries.
I'd suggest directing all the cron execution to FE, and for the task
y
Hi,
We have many cron jobs that run as part of our application. Some crons run
on FE instances and some hit our Backend instances for execution. Since
this morning, teh crons are NOT running at regular intervals. I opened 2
production issues and attached screenshots. It's our production app and