You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CRONs are pretty slow for local development. Have a few options:
--reschedule 0 * * * * * * get Cron at index 0 and reschedules it for every minute.
--immediate * * * * * * Gets all the CRONs, determines the order they would have run, and then executes them in that order per minute. For example, if there was a job that would run every hour and another every 30min, this would instead run the 30min one in one minute, then both the next minute, etc. CRONs are usually made to be over long periods, this just lets us do it quicker in development.
The text was updated successfully, but these errors were encountered:
CRONs are pretty slow for local development. Have a few options:
--reschedule 0 * * * * * *
get Cron at index 0 and reschedules it for every minute.--immediate * * * * * *
Gets all the CRONs, determines the order they would have run, and then executes them in that order per minute. For example, if there was a job that would run every hour and another every 30min, this would instead run the 30min one in one minute, then both the next minute, etc. CRONs are usually made to be over long periods, this just lets us do it quicker in development.The text was updated successfully, but these errors were encountered: