dbt Cloud Outage History

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

Read the full incident report →

Started Sep 25, 2026, 12:19 AM UTC· resolved Sep 25, 2026, 02:25 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 11:56 PM UTC· resolved Sep 25, 2026, 05:24 AM UTC

1. investigating Sep 24, 2026, 11:56 PM UTC

   GitLab is currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

2. identified Sep 25, 2026, 12:19 AM UTC

   GitLab is still currently experiencing an outage that may impact dbt customers using Studio IDE and Jobs. Customers may experience Git clone failures and other issues with functionality that relies on GitLab. We are monitoring the situation and will provide further updates as more information becomes available. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

3. monitoring Sep 25, 2026, 02:09 AM UTC

   GitLab has moved the incident to Monitoring. Services are now operational, and they’re continuing to monitor while assessing any outstanding impacts from the disruption window. For the latest updates from GitLab, please see the GitLab Status Page: https://status.gitlab.com/.

4. resolved Sep 25, 2026, 05:24 AM UTC

   This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Started Sep 24, 2026, 01:27 PM UTC· resolved Sep 25, 2026, 01:50 AM UTC

1. investigating Sep 24, 2026, 01:27 PM UTC

   We're investigating an issue with BigQuery authentication that is causing some job runs to fail intermittently. This is impacting jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) while authenticating with Google Cloud, before any queries run. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. In the meantime, rerunning a failed job or using Rerun from failure will usually succeed. Jobs using other BigQuery authentication methods, jobs on other data platforms, and dbt Studio are not impacted and should be running as expected.

2. investigating Sep 24, 2026, 03:19 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) during the token exchange with Google Cloud. We haven't found any changes on our side, and the error appears to originate on Google Cloud's side. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

3. investigating Sep 24, 2026, 05:32 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

4. investigating Sep 24, 2026, 06:41 PM UTC

   We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

5. monitoring Sep 24, 2026, 08:21 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

6. identified Sep 24, 2026, 08:59 PM UTC

   We have identified an issue with intermittent failures for jobs that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available.

7. monitoring Sep 25, 2026, 12:43 AM UTC

   The impacted component appears to be recovering, we will continue to monitor the performance. Please contact us at [email protected] with any questions or concerns.

8. resolved Sep 25, 2026, 01:50 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 11:03 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 11:03 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 11:03 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 11:03 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 23, 2026, 08:16 PM UTC· resolved Sep 23, 2026, 11:03 PM UTC

1. investigating Sep 23, 2026, 08:16 PM UTC

   We're investigating an issue with job runs that is causing intermittent failures on dbt deps. Affected runs failed with a certificate verification error while retrieving git-hosted packages. This is impacting job runs anytime after 20:16 UTC. The team is working on a resolution and we will provide updates at as soon as new information becomes available.

2. monitoring Sep 23, 2026, 08:54 PM UTC

   We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor.

3. resolved Sep 23, 2026, 11:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:54 UTC. An issue with an external dependency resulted in intermittent dbt deps failures in job runs. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →