A skipped configuration is a configuration that Configuration Resilience could not process as requested—either during a read operation or during a deployment.
Where skipped configurations are displayed
Skipped configurations are marked with a yellow clockwise arrow icon, which can appear in two places:
| Location | Meaning |
|---|---|
| Next to a configuration | CoreView was unable to read that configuration. |
| Next to the Last Update badge | The last successful read of the scope is older than expected, and CoreView may have read only some of the data for that scope. |
You cannot open a skipped configuration at property level, because its data may not be reliable. If part of the data was read successfully, that part can still be opened as usual.
Monitoring page
On the Monitoring page, select a scope from the list in the left panel. You can then review skipped configurations from two access points:
- Through the “Skipped” filter next to the “Last update” indicator
- In the Change history panel: click on the record to see more details of the skipped configuration.
Restore configurations page
On the Restore configurations page, you can review skipped configurations from two access points:
- “Last update” indicator: click the icon to open the list of skipped configurations, and select one record to see more details of the skipped configuration. To access additional troubleshooting guidance, click “Open documentation” below the error description.
- “Skipped” filter: see all skipped configurations in a single list for easier review and troubleshooting.
Baseline alignment page
On the Baseline alignment page, you can review skipped configurations from two access points:
- “Last update” indicator: click the icon to open the list of skipped configurations, and select one record to see more details of the skipped configuration. To access additional troubleshooting guidance, click “Open documentation” below the error description.
- “Skipped” filter: see all skipped configurations in a single list for easier review and troubleshooting.
Tenant alignment page
On the Tenant alignment page, you can review skipped configurations from two access points:
- “Last update” indicator: click the icon to open the list of skipped configurations, and select one record to see more details of the skipped configuration. To access additional troubleshooting guidance, click “Open documentation” below the error description.
- “Skipped” filter: see all skipped configurations in a single list for easier review and troubleshooting.
Deploy history panel
On the Deploy history panel, skipped writes (if any) are flagged on the deployment record lines. Select a record to view details about the skipped configuration, including the proposed change and the technical reason why it was skipped.
How skipped configurations are resolved
Skipped configurations usually resolve automatically at the next scheduled read. They can occur for reasons on Microsoft's side.
Skipped backup
If the same configuration is skipped for more than two backups, open a support request and include the operation ID:
- Open “Change history”
- Select the skipped property value
- Open the “Details” tab to find the operation ID
- Click on the “Copy” icon next to the ID for easier reporting
Skipped deploy
If the same configuration is skipped for more than two deploys, a banner shows a possible explanation of what caused the error. Open a support request and include the operation ID:
- Open “Deploy history”
- Select the skipped property value
- Open the “Details” tab to find the operation ID
- Click on the “Copy” icon next to the ID for easier reporting