Is Treasure AI Down?

On Thursday, Sep 3rd from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasure.ai.

On Wednesday, Sep 2nd from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasure.ai.

On Monday, Aug 31st from 01:00 to 03:00 UTC, we will be performing routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to a database used by the Treasure AI Platform. These updates are necessary to ensure we have the performance improvements available. We expect downtime to be brief, lasting about 10 minutes. The remaining time will be dedicated to verifying that all systems are functioning as expected. There may be a brief period of unavailability while we restart services, typically a few minutes. We encourage customers to retry failed requests and report any issues that persist beyond the maintenance window. See below for detailed information about the impact of this change on each Treasure Data service. We will communicate with you on an ongoing basis via our status page (https://status.treasure.ai/). If you notice any problems outside this maintenance window, we encourage you to contact our support team for assistance (https://docs.treasure.ai/support/contacting-treasure-data-support). # Impact During the maintenance window and the recovery period that follows, the impact follows one rule: - Asynchronous processing keeps working, just slower. Ingestion, jobs, and message deliveries are queued and automatically retried, and complete on their own after maintenance. - Synchronous requests return errors (mostly 5xx). Retry them after we mark maintenance complete on our status page. Degraded but usable - no action needed - Data ingestion - Streaming Import, Mobile SDKs (Android, iOS, Unity), JavaScript/Browser, Data Ingestion APIs, and Postback APIs continue to accept requests and are queued until maintenance completes. Data is imported, with a delay. For roughly 180 seconds during the window, requests may fail with a 500 error or time out; retrying afterwards succeeds. - Message delivery (Engage) - Deliveries across all channels (Email, Mobile Push) are delayed and automatically retried. - Jobs - All jobs (Presto, Hive, Data Connector Integrations, Bulk Import/Export, Result Export, Partial Delete), whether submitted from Console, API, or Workflow, or triggered on schedule, are delayed and retried until they succeed. Throughput ramps up over about 30 minutes after maintenance completes. - Table creation from SQL or Workflow - Delayed and retried after the window. - Data Workbench and Audience Studio - Jobs appear to run longer, because Parent Segment, Segment, and Workflow jobs are temporarily unavailable. Recovery follows the same pattern as other jobs. - Table preview in Data Workbench - Sample data and record counts may show stale information until maintenance completes. Returns errors - retry after maintenance - REST APIs - Job submission and cancellation; table creation; Data Connector Integrations; Plazma Public API for Spark; AI Agent Foundry and Foundry Workspace (LLM chat and conversation requests are interrupted); Workflow REST API (Workflow Projects, Audience Studio settings including Parent Segment, Segment, and Customer Journey Orchestration, and Predictive Scoring). - Presto JDBC/ODBC queries to api-presto.treasuredata.com, and queries from the CDP Segmentation UI. Scheduled Presto queries in Workflow or Console are not affected and run once maintenance completes. - Engage Studio - Operating resources (Email Domains, Sender Profiles, Campaigns, etc.). - Workflow operations in Console and CLI may fail. - ADH (Ads Data Hub), DCR (Data Clean Room), and ADL (Active Data Layer) — ADL is affected through its dependencies on the services under maintenance. What needs your attention - Campaigns scheduled during the window - check them and re-run any that failed. - Long-running workflows - workflows running longer than a few minutes may be terminated. Check and re-run them. - Integration Export jobs are not retried automatically, to avoid duplicating data in your systems. If one fails, contact support@treasure.ai to recover it. # Communication Beyond this notice, we will provide updates on our status page (https://status.treasure.ai/) approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to normal operations, and the Scheduled Maintenance will be closed. If you have any questions or concerns about this upgrade, please contact our Support team at support@treasure.ai.