We’ve identified an issue where repeated incidents are incorrectly storing the createdAt timestamp based on the original occurrence, rather than when the repeat was triggered. This could affect any workflows or reports relying on createdAt for time-based tracking.
A separate NACK_at timestamp is correctly stored and can be used as a reference. However, since createdAt is a standard field used across systems, this may cause confusion or data discrepancies in some cases.
We’re actively working on a fix. If your usage depends on the accuracy of createdAt, we recommend switching to NACK_at for now.
We’ll post updates here as we make progress.
Jun 26, 2025 - 07:49AM
(UTC)