Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Mar 07, 2024 - 22:27 UTC
Scheduled
We've identified a problem with our sync scheduler that affects some cron syncs, causing delays. The delay varies for each sync, leading to misalignment with their intended schedules, though still following the correct period / cadence for the schedule. This issue has been present in all versions of Census and has impacted some syncs that were created long ago.
For example, a sync scheduled to run every hour at the 10th minute (10 * * * *) might actually start at the 17th minute, resulting in a persistent 7-minute delay. The extent of the delay varies across syncs.
We're deploying a fix within the next day through our feature flagging system. This fix will perform a one-time internal fix to our internal representation of these schedules to correct the alignment. After the adjustment, you might notice a longer or shorter gap between syncs than usual. You can check the sync history in our UI or API for verification. You will not see any change to your sync's cron expression.
If you have any questions, please contact our support team.