Thycotic incident

All Regions - Secret Launching Errors on Secret Server Cloud and Platform

Minor Resolved View vendor source →

Thycotic experienced a minor incident on July 12, 2026 affecting Secret Server Cloud and Secret Server Cloud and 1 more component, lasting 4h 15m. The incident has been resolved; the full update timeline is below.

Started
Jul 12, 2026, 07:04 AM UTC
Resolved
Jul 12, 2026, 11:19 AM UTC
Duration
4h 15m
Detected by Pingoru
Jul 12, 2026, 07:04 AM UTC

Affected components

Secret Server CloudSecret Server CloudSecret Server CloudSecret Server CloudSecret Server CloudSecret Server CloudSecret Server Cloud

Update timeline

  1. investigating Jul 12, 2026, 07:04 AM UTC

    We are aware of an issue affecting the Delinea Platform and Secret Server Cloud where users may be unable to launch secrets, encountering the error "An error has occurred in Secret Server Cloud." Our team is actively investigating the root cause and will provide an update as more information becomes available.

  2. identified Jul 12, 2026, 08:38 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 12, 2026, 09:40 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 12, 2026, 11:19 AM UTC

    This incident has been resolved.

  5. postmortem Jul 15, 2026, 04:02 PM UTC

    ## **Incident Overview** On July 11, 2026, following a [Secret Server Cloud release](https://status.delinea.com/incidents/b8yxjwdy4kv2), customers using Session Connector launchers experienced secret launch failures, including launches brokered through the Delinea Platform. Affected launches returned an HTTP 500 error and no connection file was generated. Other launcher types and all other Secret Server functionality were unaffected. * Start: July 11, 2026, approximately 5:00 PM UTC * End: July 12, 2026, 8:34 AM UTC \(rollback completed across all regions\) ## **Root Cause and Remediation** The release changed how launcher configuration is resolved at launch time in a way that was incompatible with certain existing Session Connector launcher configurations. Launch requests for those configurations failed with a server error instead of completing normally. To remediate, our team rolled back the release across all regions. The rollback began at 8:21 AM UTC and was completed by 8:34 AM UTC on July 12, resolving the incident. Following the rollback, our team confirmed with affected customers that secret launching had returned to normal function. No action was required from customers. A corrected fix has been completed and verified with expanded automated regression coverage for Session Connector to launch configurations and will be included in an upcoming Secret Server Cloud release. No customer action will be required. ## **Preventative Actions** * Automated launch test coverage is being expanded to all supported launcher types and configurations. * Automated detection of new error signatures introduced by deployments, reducing time to detection and rollback for similar issues. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.