Treasure AI Incident History

1. resolvedOct 22 · 10:15 UTC

   The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026. Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly. We apologize for the inconvenience and thank you for your patience.

Reported by Treasure AI on their status page.

1. resolvedOct 7 · 05:24 UTC

   The recording transfer failures in Treasure AI Voice have been resolved. All systems are operating normally. Between approximately 22:55 UTC on October 6 and [fix time] UTC on October 7, new recordings could not be transferred from the mobile app. We deployed a server-side fix, and no app update is required. Recordings that failed to transfer during this period can be transferred again from the device. Thank you for your patience.

Reported by Treasure AI on their status page.

1. ResolvedOct 7 · 05:24 UTC

   The recording transfer failures in Treasure AI Voice have been resolved. All systems are operating normally.Between approximately 22:55 UTC on October 6 and [fix time] UTC on October 7, new recordings could not be transferred from the mobile app. We deployed a server-side fix, and no app update is required. Recordings that failed to transfer during this period can be transferred again from the device.Thank you for your patience.

Reported by Treasure AI on their status page.

1. resolvedSep 30 · 04:36 UTC

   Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers would have seen errors while waiting for the config changes to update. The impact is any realtime applications, personalizations, or campaigns during that window may have relied on stale batch attribute data. The system has recovered and workflows are now sending updated data.

Reported by Treasure AI on their status page.

1. ResolvedSep 30 · 04:36 UTC

   Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers would have seen errors while waiting for the config changes to update. The impact is any realtime applications, personalizations, or campaigns during that window may have relied on stale batch attribute data.The system has recovered and workflows are now sending updated data.

Reported by Treasure AI on their status page.

1. resolvedSep 29 · 21:18 UTC

   This incident has been resolved, and our support team will be following up with affected customers.

Reported by Treasure AI on their status page.

1. ResolvedSep 29 · 21:18 UTC

   This incident has been resolved, and our support team will be following up with affected customers.

Reported by Treasure AI on their status page.

1. CompletedOct 1 · 07:29 UTC

   The maintenance and validations are completed. Email campaigns, sending and delivery were not affected, and all other channels remain operation.

Reported by Treasure AI on their status page.

1. resolvedOct 16 · 00:04 UTC

   We are no longer observing any delivery delays. We have enhanced our monitoring and will continue to watch for disruptions. If you notice any sluggish delivery, please contact our support team for assistance.

Reported by Treasure AI on their status page.