Syncs triggered by sync sequences are currently not running

We have resolved this incident. All syncs triggered by sync sequences should be running normally.

We are continuing to investigate this issue. In the meantime, we wanted to further clarify behavior:

Sync sequences triggered between 7:30-8:30AM PST ran multiple times. Although there should be no duplicate data sent as a result of this, data sources may have been queried multiple times.

A subset of syncs outside of sync sequences may have also experienced a delay but should be running on schedule as expected now

Sync sequences continue to be disabled as we work to get a fix out shortly. Thank you for your patience.

We are investigating an issue that is causing an excess number of sync runs to be queued by sync sequences. We have temporarily paused syncs sequences from running.