Some customers will not be able to deploy solution packages

Final update

## Customer impact Between September 11, 2026 at 14:56 UTC and September 11, 2026 at 20:45 UTC, a subset of customers could not deploy solution packages in Solutions Management. Deployment attempts failed during package generation with a compatibility error indicating that a package version was not compatible with the expected Application runtime version. The impact was global across production environments and lasted approximately 5 hours and 27 minutes. Community environments experienced related impact beginning at 14:56 UTC. ## Root cause A regression in an internal component that manages software package versions caused the failure. During solution package generation, this component provided an incompatible package version, which caused a framework compatibility check to fail and blocked affected deployments. ## Detection The issue was first reported by a customer and then reproduced internally. The incident was created. The team confirmed the failure as a package compatibility error. ## Response At 18:42 UTC, the team identified the deployment error as a compilation failure caused by an incompatible package version. The mitigation strategy was to restore the affected component

1. Postmortem · Sep 22, 09:59 UTC
   ## Customer impact Between September 11, 2026 at 14:56 UTC and September 11, 2026 at 20:45 UTC, a subset of customers could not deploy solution packages in Solutions Management. Deployment attempts failed during package generation with a compatibility error indicating that a package version was not compatible with the expected Application runtime version. The impact was global across production environments and lasted approximately 5 hours and 27 minutes. Community environments experienced related impact beginning at 14:56 UTC. ## Root cause A regression in an internal component that manages software package versions caused the failure. During solution package generation, this component provided an incompatible package version, which caused a framework compatibility check to fail and blocked affected deployments. ## Detection The issue was first reported by a customer and then reproduced internally. The incident was created. The team confirmed the failure as a package compatibility error. ## Response At 18:42 UTC, the team identified the deployment error as a compilation failure caused by an incompatible package version. The mitigation strategy was to restore the affected component to a previously known-good version. The restore began taking effect by 18:50 UTC. By 19:16 UTC, monitoring data confirmed the restore was progressing and the incompatible version was clearing. At 19:47 UTC, the public status page was updated to reflect that the issue was identified and the fix was
2. Resolved · Sep 11, 21:33 UTC
   Issue is resolved.Start time: 15:18 UTC End time: 20:45 UTC
3. Monitoring · Sep 11, 20:49 UTC
   Fix Rollout completed in all regions. We are currently monitoring. Start time: 15:18 UTC
4. Identified · Sep 11, 19:52 UTC
   Some customers will not be unable to deploy solution packages. Issue is identified and fix rollout is in progress. Start time: 15:18 UTC
5. Identified · Sep 11, 19:47 UTC
   Some customers will not be unable to deploy solution packages. Issue is identified and fix rollout is in progress. Start time: 15:18 UTC