Rewindex

ChangesKnockWarehouse message synchronization delayed

Knock: Major incident: Warehouse message synchronization delayed

Major incidentmajor (vendor)Changed Detected status.knock.app (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Knock removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Warehouse message synchronization delayed
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-01 14:09 UTC
AddedResolved time#5
Before: not present
After: 2026-10-02 21:05 UTC
AddedUpdateidentified#6
Before: not present
After: Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected.
AddedUpdateidentified#7
Before: not present
After: We're actively re-syncing current message data into the data warehouse and expect this to complete in the next 3 hours. At that time, we will issue a new sync to all downstream destinations with up to date data.
AddedUpdateidentified#8
Before: not present
After: We're actively working on getting the most up-to-date message data for export. The job is taking an extended time to run. We are going to re-run syncs as soon as this job has completed.
AddedUpdatemonitoring#9
Before: not present
After: We have successfully rebuilt the tables for export and are running syncs now. We are continuing to monitor and will be working on some remediation and further stabilization in the coming days.
AddedUpdateresolved#10
Before: not present
After: We're back to normal sync schedules for our data warehouse connector.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Thursday, October 1

1 incident change

All Knock changesKnock profileMarkdownJSON