Saving a subcomponent and updating assemblies that contain it will resave lower assemblies that contain it.

[willyKPV7P]

I've written out the structure of assemblies I'm working in.  Each components and assembly is a different linked file.

Design Structure

Main Assembly

-Prepared Weldment

--Weldment

---Base Plate

---Other Components

--Other Components

-Other Assemblies

When I update the base plate and save it, as usual the weldment asks to update child component.  I update it and save the weldment.  Repeat with prepared weldment and repeat again with the main assembly.  I have changed nothing else.  These actions are my normal workflow for large assemblies like this and normally I have no issue.

Recently, when saving the prepared weldment, the save window mentions saving the weldment as well.  This pushes a new version of both, and locks the open file of the weldment as it is now behind a version. 

Then when saving the Main Assembly it does the same thing but asks to save the main assembly, the prepared weldment, and the weldment.  This adds another version to the weldment and prepared weldment and locks both into read only since they are now behind 1-2 versions.

This also creates a save loop since the weldment has gone up a version and now the prepared weldment wants to update child components and the whole cycle repeats.  As a result in 3 business days I've made ~10 changes to the base plate but the weldment has gone up 53 versions, maybe another 10 were changes I made manually to it.

This isn't stopping my work but it is slowing me down quite a lot.  

The closest mention to a similar issue I've seen was in 2017 and I'll paste the link below.

https://forums.autodesk.com/t5/fusion-design-validate-document/infinite-loop-of-saving-updating/m-p/...

[johnsonshiue]

Hi Willy,

There could be corruption somewhere in the design. If possible, please share the f3z file here. I would like to understand the endless file dirtying loop behavior better.

Many thanks!

[willyKPV7P]

While getting a f3z file I could send I made some developments.  I made a copy of my assemblies in fusion and trimmed out some components, since this is a company project.  I tested for the issue and it persisted.  

But, when exporting to an f3z and then uploading back to fusion and attempting to recreate the issue it no longer occurs.  

I'm still open to suggestions but I'll start by rebuilding the assemblies and report back if I learn anything.

[johnsonshiue]

Hi Willy,

Many thanks for sharing the file! I took a quick look but I could not reproduce the behavior. I suspect there could be some sort of corruption with the design file in the cloud, though I cannot say it definitely. But the fact that the reloaded version works better is a hint.

If you find any repeatable pattern, please let us know.

Thanks again!