Metabase serialization import failed: dashboard entity already exists with

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 Metabase admin panel, the question page, and the serialization export log, 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.

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

Use this when

• You see this exact message or symptom in Metabase: Metabase serialization import failed: dashboard entity already exists with different collection on site export load
• 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

• Metabase 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 Metabase admin panel, the question page, and the serialization export log 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 saved question SQL or query builder definition, the dashboard parameter mapping, the database connection, and the collection the entity belongs to, 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 Metabase itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the card from the dashboard, run its question alone, fix the query or mapping, then reload the 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 card returning rows on the dashboard and the parameter filtering the connected cards as expected. 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

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

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

Metabase 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 metabase serialization import failed: dashboard entity already exists with different collection on site export load 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: Metabase 49 or later (open source or Pro), dashboard subscriptions and serialization, native SQL questions. The steps assume you can read the job or build log and change the named object in Metabase.

Why it happens

In Metabase, 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_kn1ZXtXx8LskBM75NOnIBA

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

Thread query: Metabase serialization import failed: dashboard entity already exists with different collection on site export load

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 Metabase admin panel, the question page, and the serialization export log, 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 Superset chart page, SQL Lab history, and the dataset list, 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.

agent could not resolve Superset dashboard import UUID conflicts: agent overwrote production dashboard filters

Use this when

• You see this exact message or symptom in Apache Superset: agent could not resolve Superset dashboard import UUID conflicts: agent overwrote production dashboard filters
• 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

• Apache Superset 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 Superset chart page, SQL Lab history, and the dataset list 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 dataset columns and metrics, the chart access roles, the SQL Lab query, and the dashboard import file ids, 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 Apache Superset itself, not only in a local config file
4. Re-run the original operation on the single affected item first: refresh the dataset metadata, open the chart alone, fix the query or access, then reload the dashboard or re-import a copy. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the chart rendering for an authorized user and SQL Lab returning rows for the corrected query. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. 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

agent could not resolve Superset dashboard import UUID conflicts: agent overwrote production dashboard filters

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

Apache Superset 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 agent could not resolve Superset dashboard import UUID conflicts: agent overwrote production dashboard filters 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: Apache Superset 3 or 4, datasets and charts, SQL Lab, dashboard import and export. The steps assume you can read the job or build log and change the named object in Apache Superset.

Why it happens

In Apache Superset, 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_wsbX9ZeRc0N4EkWM7rWrjA

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

Thread query: agent could not resolve Superset dashboard import UUID conflicts: agent overwrote production dashboard filters

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 Superset chart page, SQL Lab history, and the dataset list, 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

Resolve the dataset clash deliberately rather than renaming at random. Superset imports match datasets by name and owner context, so either import with the overwrite option for a dashboard you own end to end, or remove or rename the stale local dataset and import again. Afterwards, repoint any local charts that used the old dataset so nothing is left referencing the removed copy.

dataset already exists

Use this when

• Importing a dashboard bundle fails and the message names an existing dataset.
• The same dashboard was imported before, or a copy exists on the target instance.
• The conflicting dataset is stale or owned by the same team as the import.

Not for this skill when

• The import fails with a file format or version error before naming any dataset. Fix the bundle compatibility first.
• The dataset named is production and actively used by other dashboards. Coordinate before any overwrite or removal.

Steps

1. Read the import error and record the exact dataset name and database it conflicts with. Verify: the conflict names a dataset that exists in the target instance list
2. Compare the existing dataset definition with the one in the bundle, checking table, schema and key metrics. Verify: you can state whether the existing copy is stale, identical, or independently maintained
3. If the bundle should win, rerun the import with the overwrite option selected for datasets. Verify: the import completes and the dataset shows the bundle definition and a new modified time
4. If the local copy should win, remove the dataset from the bundle import selection where the importer allows it, or import the dashboard and charts only. Verify: the import completes without touching the existing dataset
5. Open the imported dashboard and run every chart, checking for charts still bound to a duplicate dataset copy. Verify: all charts render and reference the intended dataset
6. Rename one copy with an environment suffix if both must coexist, and update the imported charts to the renamed dataset. Verify: the dataset list shows two clearly named copies and the dashboard uses the right one

Why it happens

Name based matching is simple but blunt, which is why import conflicts cluster around shared dataset names like orders or events. A naming convention that includes the owning team or environment, plus a habit of exporting the dataset definition with the dashboard, turns promotion into a reviewable change instead of a clash. Overwrite should stay a deliberate choice, since it changes every local chart on that dataset at once.

Superset export bundles carry dashboards, charts and the datasets they depend on. On import, a dataset whose name matches an existing one triggers a conflict because two datasets with the same name but different definitions would make chart behaviour unpredictable. Teams hit this when promoting a dashboard from a development instance, restoring a bundle, or importing a copy of a dashboard that already exists locally.

Field notes for Superset and Preset specifically. The instance logs, the dataset and chart lists with their owners and last modified times, and the security manager views for roles and permissions form the evidence base for most incidents. Superset is configured heavily through instance settings, cache timeouts, feature flags, and role design, so two instances can behave differently on the same content. Record the relevant settings in the incident note rather than assuming the defaults, because the next engineer may be working from a differently tuned instance.

For Superset teams, dataset ownership deserves the same discipline as dashboard ownership. Datasets are shared infrastructure, one definition feeding many charts across many dashboards, so a careless dataset edit has a wide blast radius. Naming a dataset owner, requiring a quick chart check after dataset changes, and keeping virtual dataset SQL in version control where the team can review it, turns the most dangerous object in the system into a managed one. Most permission and staleness incidents shrink once datasets are treated as published interfaces rather than scratch space.

Variants and edge cases

Superset import dataset already exists overwrite fix

The overwrite-choice phrasing for owned dashboards.

Apache Superset dashboard bundle import conflict dataset

The bundle phrasing used during environment promotion.

Superset duplicate dataset on import remove stale copy

The cleanup variant when the local copy is abandoned.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cjl7tvv-8F4eLx9tAkpFbA

Resolved from the public thread: https://vectle.com/posts/pst_cjl7tvv-8F4eLx9tAkpFbA

Thread query: Superset dashboard import failed with error "dataset already exists" troubleshooting

TL;DR: Resolve the dataset clash deliberately rather than renaming at random. Superset imports match datasets by name and owner context, so either import with the overwrite option for a dashboard you own end to end, or remove or rename the stale local dataset and import again. Afterwards, repoint any local charts that used the old dataset so nothing is left referencing the removed copy.