NA

that depends on the load of the scheduler running the workflow and how many workflows are running at your set time, best to simply check the start time for a bunch of your cron deployments so you can gather the variance numbers

Actually just by looking at the deploy logs would suffice

But thanks Brody. Seems like they have been running within 5 to 7 seconds of what I dictate it to be

yep that would be normal at this time

I'm looking at the more popular timestamp which is 00z and it appears to be offset by about a minute. Generally it is fine for my use case :)

that would also be normal, crons should run but they dont guarantee minute accuracy

The more accurate would be an in-code scheduler isn't it. I'm currently doing this but I'm trying to eliminate idle resources, that's why I'm slowly switching some of my smaller services to railway cronjobs

Let's just say I haven't really been efficient at all with my in-code cronjobs.

yeah ms level accuracy would be done with an in code scheduler but of coruse that comes with idle resources like you said, so there are trade offs to either options

Anyways to answer the question seems like it can be anywhere around 5 seconds to 1 minute after the stipulated time.

Keyword: AFTER. So it always happens after

I'll mark this as solved now. Thank you

no problem!