> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.
# History and environment status
> See every promotion applied to an environment, what it changed, and what has been changed directly in the environment since.
The **History** tab of **Configuration promotion** shows two things for the environment you are in. **Environment status** describes its configuration now. **Promotions applied to this environment** is the record of every promotion into it.
## Environment status
| Part | What it shows |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Current configuration** | A short fingerprint of this environment's configuration, how many entries it holds, and when it was checked |
| **Last promotion** | The fingerprint right after the last promotion, and when, by whom and with what status it was applied |
| **Changes since the last promotion** | Configuration **added here**, **modified here** or **removed here** since that promotion, limited to the types it carried |
| **Not promoted, maintained elsewhere** | Areas that are enforced here but never read or written by a promotion, so a plan with no differences does not cover them |
Select **Check now** to read the configuration again.
If the fingerprints match and nothing is listed, the environment still holds exactly what the last promotion left. Changes listed since the last promotion were made directly in this environment. The next promotion would overwrite them. Before you promote into the environment, either bring those changes into the source environment or record them as [kept different](/configuration-promotion/rules-and-differences#kept-different-in-this-environment).
If a part of the product could not be read, for example because workflows were unreachable, its types are listed separately. The fingerprint and the change list then leave those types out.
## Promotions applied to this environment
The list shows the latest 50 promotions, newest first:
| Column | Meaning |
| ------------------- | ------------------------------------------------------------------------ |
| **When** and **By** | When the promotion started and who applied it |
| **Status** | **Completed**, **Failed** or **Running** |
| **Version** | The configuration fingerprint before and after the promotion |
| **Changes** | How many changes were applied, failed, rolled back, not run or left over |
| **Comment** | The comment entered when applying, such as a change request reference |
Open a row by its date to see the counts, the reason for each failed change, and the group mappings the promotion used. **Leftovers (not ticked or blocked)** lists the changes that were not applied and why. **Changes in this promotion** gives the outcome of each change:
| Outcome | Meaning |
| --------------- | --------------------------------------------------------------------------------- |
| **Applied** | The change was saved |
| **Failed** | Saving the change failed; the reason is shown |
| **Rolled back** | The change was saved together with a change that failed, so it was undone with it |
| **Not run** | The change came after a failed step, so it was skipped |
The record of each promotion is shown to everyone who can open the page. The individual changes, leftovers and mappings are shown only for the configuration types you can view.
### Correcting a promotion
A promotion cannot be undone from History. The configuration is saved as a version before and after each promotion to produce the fingerprints and the change list, but there is no step that restores it. To correct what a promotion applied, fix it in the source environment and promote again. If the environment must differ on purpose, record it as [kept different](/configuration-promotion/rules-and-differences#kept-different-in-this-environment).
When a promotion fails part way, the steps saved before the failure stay saved. Open the promotion in History to read which change failed and why. Fix the cause, then import the same file again: what was saved now shows as unchanged, and the rest can be applied.
## Troubleshooting
| Symptom | Likely cause | What to do |
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Configuration promotion** is missing from **Admin settings → General** | You do not hold **Keyword configuration administration**, or the feature is not enabled for the environment | Ask for the permission. If you hold it, contact your consultant team about availability |
| The export file lacks a configuration type | You cannot view the type, or that part of the product is not available in the source environment | Ask for the view permission of the type, or check that the feature is available |
| **Import refused**: the file holds configuration you may not see here | The file holds a type you cannot view in this environment | Ask for the view permission, or export again without that type |
| **Import refused**: the file is inconsistent | The file was changed after export | Export again, and do not edit the file |
| **Import refused**: a name exists twice here | Two entries of the same type share a name in this environment | Rename one of them here, then import again |
| The import reports an unknown entity type | The environments run different releases, or a part of the product is not available here | Promote between environments on the same release, and export only types the target has |
| A change is blocked because a user group does not exist here | The group name differs between environments, or the group has not been created | Add a [reference rule](/configuration-promotion/rules-and-differences#user-group-reference-rules), or create the group |
| A change is blocked because it needs a permission | You can view the type but not change it | Ask for the permission, or leave the change to someone who holds it |
| Apply is refused and the review refreshes | This environment's configuration changed after the preview | Review the refreshed plan and apply again |
| The promotion status is **Failed** | A step failed while saving | Open the promotion in History, fix the cause of the failed change, and import the file again |
| A script or workflow fails after a promotion because a value is missing | Secret values and credential-like variable values never travel | Set the values in this environment |
| The same delete appears on every import | The entry exists here but not in the source | Delete it here if it is no longer needed, or record it as kept different |
## Where to read next
What changed in Nobly Insight, release by release — written for the people who use and administer it.
What a promotion covers, what it never moves, and the permissions it needs.