I just had a Postgres trigger that is built to look for new rows added to a database start firing off events for every row that was already in the database. Is there a way to look into what caused already existing rows to cause “new row” events in the source? This trigger/workflow has been running for a little over 10 days and had been working as expected until an hour or so ago.
Please let me know what information you need in order to dig into the issue.
Last night around 8:00 EST / 5:00 PST we had an incident with the deduplication system that prevents remitting of duplicate events. It was fixed by 8:30 EST. We’re doing a post-mortem on this incident and really appreciate your patience.
It wasn’t an issue with your Postgres database or the Postgres component, just the underlying platform.