Transform North America: Job Execution Service Interruption

Final update

North American Transform Customers, We successfully completed our scheduled outage this morning but some of our customers are experiencing job execution failures due to changes we made during the outage. During the scheduled maintenance we took a series of steps to increase the scale of our cloud infrastructure, which is now fully utilizing all of our documented outbound network range for our Google Cloud us-central1 region. If you have a Data Platform network policy defined, please confirm and update your IP address allowed list to include the full set documented here under the “US | Google | us-central1 | Iowa” section: https://docs.coalesce.io/docs/setup-your-project/setup-requirements/network-requirements Ensure you have the full list configured, not only the addresses that are new to you. Coalesce may connect from any address in this range, and which one it uses on a given connection is not fixed. Allow-listing a subset can appear to work and then fail later. We apologize for the disruption. Please reach out to our Support Team with any questions.

1. Resolved · Jul 25, 17:02 UTC
   North American Transform Customers, We successfully completed our scheduled outage this morning but some of our customers are experiencing job execution failures due to changes we made during the outage. During the scheduled maintenance we took a series of steps to increase the scale of our cloud infrastructure, which is now fully utilizing all of our documented outbound network range for our Google Cloud us-central1 region. If you have a Data Platform network policy defined, please confirm and update your IP address allowed list to include the full set documented here under the “US | Google | us-central1 | Iowa” section: https://docs.coalesce.io/docs/setup-your-project/setup-requirements/network-requirements Ensure you have the full list configured, not only the addresses that are new to you. Coalesce may connect from any address in this range, and which one it uses on a given connection is not fixed. Allow-listing a subset can appear to work and then fail later. We apologize for the disruption. Please reach out to our Support Team with any questions.
2. Identified · Jul 25, 16:24 UTC
   We have identified a downstream issue from our scheduled maintenance that is effecting job execution. We will update this issue when resolved.