*Maintenance* and system *recovery* have been fully completed.
The Workflow database maintenance is now complete.
Posted Jul 11, 2020 - 21:51 PDT
Verifying
The scheduled Workflow database maintenance is complete.
We are monitoring the system closely to ensure all systems successfully complete their *recovery* and return as quickly as possible to full functionality and throughput.
Posted Jul 11, 2020 - 21:29 PDT
In progress
The scheduled Workflow database maintenance is starting now.
We expect the operation to cause approximately 3 minutes of downtime and to be followed by a *recovery* period of around 5 minutes during which the system will gradually reach back to full throughput. During the maintenance and recovery, customers may experience workflow REST API unavailability, delays with scheduled user-defined Workflow session executions, CDP Master Segments, Batch Segments, API Tokens, and Predictive Scoring creation and update failures, and delays in refresh of Master Segments, Batch Segments, and Predictive Scoring.
Posted Jul 11, 2020 - 21:15 PDT
Scheduled
In about 30 minutes, from 21:15 PDT (13:15 JST) we will be performing maintenance on the Workflow database.
The maintenance is necessary to upgrade the instance the PostgreSQL database is running on.
We expect the operation to cause approximately *3 minutes of downtime*.
# Impact
The database will become unreachable for the duration of the *maintenance* procedure, expected to last for approximately 3 minutes. This will be followed by a *recovery* period of around 15 minutes during which the system will gradually reach back to full throughput.
All internal components reading/writing the Workflow Database have built-in fault tolerance that will allow them to retry the request in case of failures: when the connection encounters an error, the request is retried several times and for long enough to ensure maintenance and recovery periods are successfully completed.
For customer facing components, connection/request failures may be reflected back directly on the caller: they should be interpreted as a suggestion to retry the connection/request later, most practically after the maintenance window is closed.
During the maintenance and recovery, customers may experience the following:
* Workflow REST API unavailable All Workflow REST API endpoints will be unavailable during the maintenance and will respond with a 500 error code.
* Delay in the execution of Workflow scheduled sessions The execution of all scheduled Workflow sessions will be delayed during the *maintenance* period and remain queued. During *recovery*, we expect the sessions to begin processing slowly: within 5 minutes the processing of queued sessions should reach regular capacity and the backlog should be depleted shortly after.
* CDP Master Segments, Batch Segments, API Tokens, and Predictive Scoring creation and update unavailable Throughout the *maintenance* period, it won’t be possible to create and update Master Segments, Segments, API Tokens, and Predictive Scoring: these functionalities rely on the Workflow functionality to execute ETL tasks. The ability to create and update will remain impaired during the *recovery* period and will be restored shortly after.
* Refresh of CDP Master Segments, Batch Segments, and Predictive Scoring refresh Refresh of CDP Master Segments, Batch Segments, and Predictive Scoring refresh all rely on the Workflow functionality to execute. As for Workflow session executions, refresh will be delayed during the *maintenance* and *recovery* periods.
Beyond this notice, we will provide updates at the start and completion of the operation and once the verification of the new system is completed: at that time, all systems will have returned to full functionality and this Scheduled Maintenance will be closed.
Posted Jul 11, 2020 - 20:50 PDT
This scheduled maintenance affected: US (Workflow).