Not supported on Cloud Service
Custom run modes are not possible on AEM as a Cloud Service
Adobe's notable changes state that additional or custom run modes are not possible. Configuration folders such as config.uat or config.author.qa are ignored.
What to use instead
config.author, config.publish and combinations with dev, stage, prod and rde; values that differ between environments of the same type come from Cloud Manager environment variables.
How to fix it
- List config.* folders and map each to a supported run mode.
- Replace environment differences with $[env:...] placeholders.
- Remove code that branches on run mode names.
How we detect it
- Readiness scan rule
custom-runmode: Custom run modes.
Best Practices Analyzer reports it under URC.
Can agents fix it?
Partial. Mapping needs a decision per environment.
Source: Adobe Experience League. Checked 19 October 2026.