641be8fec3
no issue - typically cron/later schedules will schedule for :00 on the minute which would create API spikes with every members-email-using Ghost site hitting the API at the same time - adjusted the scheduling to use cron syntax with job runs every 2 minutes on 1,3,5... or 2,4,6... and a random seconds value to smooth usage across sites |
||
---|---|---|
.. | ||
client@ad3460a4e8 | ||
frontend | ||
server | ||
shared | ||
index.js |