Grafana provisioning error: dashboard with the same uid already exists folde

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

Use this when

• You see this exact message or symptom in Grafana: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Thread query: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. The named signal in this one is error 412. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

Use this when

• You see this exact message or symptom in Grafana: Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana error 412 during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iWcWigZ7YeDdxr0ELRGqQw

Resolved from the public thread: https://vectle.com/posts/pst_iWcWigZ7YeDdxr0ELRGqQw

Thread query: Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. The named signal in this one is error 412. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Read the provisioning error in the Grafana server log first, because it names the file and the parse problem. Fix the JSON syntax or the schema mismatch in that file, such as a dashboard exported from a newer Grafana version or a file with a wrapper object the provider does not accept, and restart or wait for the provider rescan. Provisioning is strict, one invalid file can block its whole provider folder.

Grafana dashboard provisioning failed: JSON model invalid error on startup fix

Use this when

• Provisioned dashboards are missing after a restart, upgrade, or a Git sync of dashboard files.
• The Grafana server log shows a provisioning error naming a dashboard file.
• Dashboards created in the interface on the same instance work normally.

Not for this skill when

• A single interface created dashboard fails to load. That is a dashboard content issue, not provisioning.
• The data sources provisioned from the same system also failed. Check the provisioning configuration root first.

Steps

1. Search the Grafana server log for provisioning errors and record the file name and message for the first failure. Verify: the log names one file and one concrete parse or validation problem
2. Validate that file with a JSON parser to separate a pure syntax error from a schema problem. Verify: the file either fails parsing at a known position or parses cleanly
3. If the file carries the export wrapper, extract the inner dashboard object, and if the schema version is newer than the instance, downgrade or upgrade deliberately. Verify: the file top level is the dashboard model itself with a supported schema version
4. Check the provider configuration for the folder path, the folder name, and update behaviour so the loader reads the corrected file. Verify: the provider points at the folder that actually contains the file
5. Restart Grafana or wait for the rescan interval, then watch the log for a clean provisioning pass. Verify: the log shows the dashboard provisioned without an error
6. Open the provisioned dashboard in the interface and confirm it renders and carries the expected update behaviour for edits. Verify: the dashboard appears in its folder and panels load

Why it happens

Provisioning treats dashboards as code, so it inherits code discipline problems, hand edited JSON, version skew between instances, and export formats pasted into source files. Validating dashboard files in the same pipeline that ships them, with a JSON check and a schema version matched to the target Grafana, makes provisioning failures a build error instead of a startup surprise.

File provisioning loads dashboards from disk at startup and on a rescan interval. The loader validates each JSON model before saving it, and rejects files with syntax errors, unknown schema versions, or the export wrapper format that includes extra top level keys. Because the failure happens outside the interface, the instance looks healthy while the provisioned folders stay empty, and only the server log explains why.

Field notes for Grafana specifically. The server log at startup and the provisioning and alerting sections are where instance level truth lives, and the dashboard JSON model view in the interface shows exactly what Grafana stored, which settles most arguments about what a panel is really querying. Grafana changes behaviour across versions in the alerting and provisioning areas especially, so record the version in every incident note. Instances managed as code should treat the Git copy of a dashboard as the source to fix, with interface edits treated as drafts to be ported back.

A Grafana habit that prevents repeat incidents is to keep one small health dashboard for the monitoring system itself, showing data source query success, alert evaluation state, and provisioning status. Monitoring the monitor sounds recursive, but the failures in this family are silent by nature, empty variables, unevaluated rules, missing dashboards, and a health view is the only surface where silence itself becomes visible. Checking it after every upgrade, migration, or provisioning change catches the breakage in the same hour it was introduced.

Variants and edge cases

Grafana provisioning failed invalid dashboard JSON startup

The startup phrasing matching the log symptom.

Grafana provisioned dashboard missing exported wrapper JSON

The wrapper variant for files saved from the share export dialog.

Grafana dashboard schema version too new provisioning error

The version skew variant between instances.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CfS8taqJlL07aVui6aJOFg

Resolved from the public thread: https://vectle.com/posts/pst_CfS8taqJlL07aVui6aJOFg

Thread query: Grafana dashboard provisioning failed: JSON model invalid error on startup fix

TL;DR: Read the provisioning error in the Grafana server log first, because it names the file and the parse problem. Fix the JSON syntax or the schema mismatch in that file, such as a dashboard exported from a newer Grafana version or a file with a wrapper object the provider does not accept, and restart or wait for the provider rescan. Provisioning is strict, one invalid file can block its whole provider folder.