Configured Design permanently crashes on open/export

[loganskylersmith]

My file "FERGUS REV 2" crashes Autodesk Fusion (v2705.1.15, macOS 26.6) every time I try to open it. 

Crash signature (identical across every attempt):

DesignConfigurationTableRow::rowDataStringVector
← DesignConfigurationTable::addTestRow
← PIMTableSerializer::deserializePIMTableData / deserializeDataForTable / deserializeFromData
← DesignConfigurationMgr::initTable(s) → assetFullyInitialized

What I've already tried, all failing identically:

• Cleared local cache and let Fusion re-download the file fresh from the cloud — same crash.
• Opened an earlier version from version history — same crash, confirming the corruption is in the Configurations table itself, not the edit history.
• Exported as Fusion Archive (.f3z) from the web — import throws an XML error.
• Tried exporting as STEP from the web — not available/fails for this Configured Design.

This points to corrupted data in the design's Configurations table that's blocking every access path (open, re-download, version rollback, and export). Since this needs server-side repair, could someone from Autodesk take a look at this file? Happy to share the file ID/URN and crash logs if needed.

[dsouzasujay]

Hi @loganskylersmith ,

Thanks for the detailed information and for listing everything you have already tried.

Since the design is crashing consistently during initialization and you are also unable to recover it through an earlier version or web export, I would like to take a closer look at the affected project and file.

• How to save a local archive (backup) file in Autodesk Fusion
  • From the Autodesk Account Dashboard

Could you please invite me to the Fusion project containing FERGUS REV 2 using:

Sujay<dot>dsouza<at>autodesk<dot>com

Once I have access, I can investigate the configured design and work with the appropriate development team if needed.

If available, please also send the file ID/URN and any crash report/CER details associated with the crashes.

[Steven_Gao]

Hello @loganskylersmith, sorry to hear the crash issue of your Configuration dataset. It looks like the configuration table has corrupted. Besides inviting Sujay into your hub for further investigation, can you have a try the following method to see whether the issue can be resolved?

• Launch Fusion
• Run the following text command before opening the dataset: DesignConfig.FetchTableFromCache /on
• Then try to open the problematic dataset. If open the file successfully, you can make a small change to the configuration design and save it again—for example, duplicate a configuration row in the Configuration table and then delete the new added row.

After that, either run text command: DesignConfig.FetchTableFromCache /off  or restart Fusion after the dataset has been repaired and saved.

Please let me know whether the above method resolve your problem or not.

Thanks,

Steven

[loganskylersmith]

Hi Steven,

Thanks for the suggestion! I gave it a try:

1. Opened Text Commands (Option+Cmd+C on Mac)
2. Ran: DesignConfig.FetchTableFromCache /on
3. Tried opening FERGUS REV 2

Unfortunately it still crashes — identical crash signature to before (DesignConfigurationTable::addTestRow → DesignConfigurationTableRow::rowDataStringVector via PIMTableSerializer). I checked a fresh CER crash log from this attempt and it matches the earlier ones exactly, so the cache-source toggle didn't change the outcome for this file.

I've also reached out to Sujay via email with a full crash report package (summary + two crash dumps) since he offered to look at the project directly. Given that open, re-download, version rollback, export, and now this cache workaround have all failed identically, it seems like the corruption is deeper than something a client-side flag can route around.

Appreciate you taking the time to suggest this — let me know if there's anything else worth trying on my end in the meantime.

Thanks,
Logan

[pkomatlapalli]

Hi @loganskylersmith ,

Hope you are doing well!

We wanted to check if you are still experiencing this issue. If the issue persists, please provide any additional details or relevant information so we can further investigate and assist you.

If you have already found a solution, could you please share it with us? Your feedback may help others facing the same situation.

[Steven_Gao]

@loganskylersmith It's a regret to hear the method not working for you. I have logged an internal defect(ID: FUS-276592) to track this issue. Our development team will do some investigation of your dataset later. 

In addition, can you have a try to open some old versions and see whether they can be opened successfully? If yes, you can save it as latest and continue your work(but you may lost some work on the latest version(s)).

Thanks,

Steven

[DanioZhu]

Hello @loganskylersmith ,

Thanks for the details. They helped us identify the cause of the crash.

While we are still investigating the root cause, please try the steps below to open the design and save a repaired copy.

Steps:

1. In Fusion, open the Text Commands panel.
2. Type each of these commands and press Enter after each one:
   • DesignConfig.SetTestVersion 1
   • DesignConfig.FetchTableFromCache /on
3. Open FERGUS REV 2 from the Data Panel.
4. Before doing anything else, open the configuration table and check that your configurations and their values are all there.
5. Only if everything looks correct: modify a cell value, then change it back so the design is marked as modified. Save the design. This writes a repaired version of the table back into the file. Wait until the design save and upload are complete.
6. Close Fusion and start it again. This switches the settings from step 2 back off. Then open the design normally to confirm it opens without crashing.

Important

• If the design opens but the configuration table is empty, don't save. Close the design without saving and reply here, so we can look at the cloud copy of your table.
• The next time you open the design after saving, the preview row at the top of the table will be reset to match the active configuration (i.e. test row). None of your configurations are affected.
• If Fusion still crashes at step 3, please reply here and send the crash report from that attempt. It helps us confirm what's going on.

Please tell us how it goes.

Thanks,

Danio