Is Copado down?

Issue Summary: Salesforce has officially acknowledged an ongoing global service disruption affecting their Core Services. This infrastructure-level outage is the root cause of the intermittent maintenance errors and access issues currently affecting our environments. Current Status: Provider Incident ID: https://status.salesforce.com/incidents/20004433 Root Cause: Global Salesforce Core Service disruption. Next Steps & Actions: Track Real-Time Updates: Please monitor the official Salesforce Trust Link for direct updates from Salesforce engineering. Support Ticket Request: We kindly ask that you continue to refrain from opening Copado Support or IT tickets regarding this specific error, as our support teams do not have direct control over underlying platform restoration. We are closely monitoring Salesforce's progress and will post another update as soon as platform functionality stabilizes.

Current Status Salesforce has deployed a fix across their infrastructure, and service is actively returning to normal across affected instances. Our team has updated our status to Monitoring as platform performance stabilizes. Incident Progress Service Restoration: A fleetwide rollout by Salesforce is currently in progress, and system availability is restoring. Permanent Resolution: In parallel with the rollout, engineering teams are implementing a permanent, code-level fix to prevent recurrence. Internal Monitoring: We are actively monitoring error rates and telemetry to verify complete stability. Customer Guidance Most users should now be able to access their Copado instances and Copado Community without encountering maintenance errors. If you experience any residual latency or brief hiccups, please wait a few moments and refresh your browser session.

This incident has been resolved.

We are currently investigating reports from a small number of customers regarding unexpected job executions. Our team is actively reviewing the behavior and working to better understand the issue. While we are currently investigating this, please feel free to open a case through our Success Community if you are experiencing any related issues.

We are still actively investigating this issue and working toward a resolution. We will update this status with more information as it becomes available.

We are no longer receiving reports of unexpected job executions. We are working with Salesforce to determine the root cause and will continue to monitor for any recurrence.

We have confirmed that the root cause of this issue is a known Salesforce product bug. Salesforce is actively working on a fix and is currently planning to make it available as an Early Release. Details can be found here: https://help.salesforce.com/s/issue?id=a02g7000007hHG5AAM We are marking this incident as resolved.

We are currently tracking Salesforce service degradation impacting org authentication and Copado deployments. We are monitoring the situation closely and will provide further updates as they become available. Check status.salesforce.com for additional details.

The Salesforce degradation invalidated active Refresh Tokens, causing Copado jobs to lose access to their connected orgs. To restore functionality, please perform the following steps: 1. Re-authenticate your Copado user credentials to generate new, valid refresh tokens. 2. Retry any failed Copado jobs. If you continue to experience any issues after re-authenticating, please reach out to our support team for assistance.

We have determined that there were no additional occurrences in the last hour. This incident has been resolved.