You can’t list or selectively clear “pending” environment settings one by one, but you can understand what’s pending and how to get rid of the warning.

1. What “pending environment settings” actually are

In OS11, any change to Environment Settings in Service Center (Administration > Environment Configurations, Security, Email, DB Connections, etc.) can create pending runtime / compile‑time configurations for the whole factory. These stay in a pending state until either:

• You click “Save and Apply Settings to the Factory”, or
• You publish/redeploy modules/solutions, which applies any pending settings for those modules. Applying Configurations in Service Center

Even if you revert a field (e.g. Hostname, Environment Name) back to its original value, the platform still considers that a configuration change that must be applied, so the warning remains until the pending configuration is processed.

2. Where to see what might be pending

There’s no “diff” screen showing exactly which setting values are pending, but you can narrow down the source as follows:

1. Environment Configurations screen

   • Go to Service Center > Administration > Environment Configurations.
   • If there are pending changes, you’ll see the warning banner and the “Save and Apply Settings to the Factory” button enabled.
   • Any change saved here (even reverted) can generate pending runtime or compile‑time settings. Applying Configurations in Service Center

2. Other environment‑level screens
   Check these as well, because changes here also create pending settings:

   • Administration > Security > Environment Security
   • Administration > Security > Network Security
   • Administration > Email
   • Administration > Database Connections
   • Administration > Certificates
     If the warning appears on these pages, it means there are environment‑level changes waiting to be applied. Applying Configurations in Service Center

You won’t see a list like “Pending: Hostname, Date Format…”, but the presence of the warning on a specific administration page tells you that some setting on that page was changed and is pending.

3. How to clear the warning

Since “Apply Settings to the Factory” is failing in your case, your options are:

Option A – Apply settings through a solution (partial factory)

If the failure is caused by a specific module, you can try applying pending settings only to a subset of modules:

1. In Service Center, create a Solution:
   • Include the modules/applications you actually use (or a broad set, if practical).
2. On the Solution detail screen, click “Apply Settings” (not “Publish”).
   This applies pending runtime settings to those modules without a full factory reload. Applying Configurations in Service Center

If the error only happens when hitting “Apply Settings to the Factory”, this approach sometimes bypasses the problematic module and clears the warning for most components.

Option B – Full republish with full compilation (for compile‑time settings)

Some environment settings (e.g. Date Format, Debug mode) are compile‑time. For these, a normal republish may not be enough to fully reset all modules after a platform upgrade or heavy changes. Applying Configurations in Service Center

A common workaround:

1. Create a Solution containing all modules of your factory.
2. In Service Center, publish this solution using “Publish with full compilation” (checkbox in the publish dialog).
3. After it succeeds, try “Save and Apply Settings to the Factory” again.

This approach has cleared stubborn “pending configuration changes” in environments that had been upgraded or had inconsistent compile‑time states.

4. If “Apply Settings to the Factory” always fails

Since you confirmed:

• All eSpaces are published and working, and
• The warning persists,

then something in the apply step itself is failing (e.g. a module that no longer exists, a corrupted module, or an internal platform error). This is similar to the case where “Apply Settings” fails due to a module not yet published or deleted. Applying Settings for Factory.

In that situation:

1. Check Service Center > Monitoring > Error Logs around the time you trigger “Apply Settings to the Factory” to see which module or operation is failing.
2. If the logs point to a specific module:
   • Try to republish that module individually, then re‑run “Apply Settings to the Factory”.
3. If the issue isn’t clear from logs, or if the factory‑wide apply consistently fails despite republish/full compilation, open a ticket with OutSystems Support so they can inspect the platform state at the database level.

5. Can you “clear” pending changes without applying them?

No. There isn’t a supported way to “discard” pending environment configurations; the only way to remove the warning is to successfully apply them (either:

• to the whole factory, or
• to all modules via solutions/publish).

If your environment is working as expected and the warning is purely cosmetic but you still can’t apply settings, that typically warrants a support ticket, because it means the platform’s internal configuration state is inconsistent.

Summary:

• You can’t directly list or delete individual pending environment settings.
• You can see which pages have pending changes (Environment Configurations, Security, Email, etc.) and apply them via solutions or “Apply Settings to the Factory”.
• If factory‑wide apply fails, use a solution + Apply Settings, or full compilation publish, and check error logs.
• If that still fails, it’s likely a platform issue that needs OutSystems Support intervention.