Failing to save ... a configuration?

[ltomuta]

The failing design does not actually exist, it is just a configuration that resides in a design with a different name. I used this config recently (derived into a Manufacturing Model) so I guess that's why it gets saved but ... why exaclty does it get saved? Where does it get saved? Are configurations cached somehow?

If I click on "Open design" it opens the desing containing this configutation but that design is not in a "dirty" state and no save is possible/required.

[jhackney1972]

There is a published workaround to Uploading a configuration to the cloud that may help you until they release a fix.  You will find it in this post, message #4.

[joe.mills]

When Configurations are first referenced in an assembly (e.g. insert or derive) we generate a file version for that Config and save it to the cloud in the background.  As with normal saves, this can there could be many causes for the save failure.

Can you share your log files to help us diagnose the issue? You can get log files from Help > Support and Diagnostics > Diagnostic Log Files.

[joe.mills]

This does not appear to be the same issue. The issue you mention is related to uploading exported Configured Designs via the Upload button. In this case, the save failure is an for an individual Configuration, which can only be saved by the system when referencing them in assemblies.

[ltomuta]

So the config is only saved on first use, not on creation?
That may make sense resource wise but it did feel like it takes extra time to just access a new config (select design to derive -> pick config -> slooooooow -> open design for derive selection -> slooow -> have the derive created in target design).

I will collect the logs tomorrow and DM them to you, maybe there's something to be learned from there. 

As a related piece of feedback, I would love to see an option that once I select a config to have the top level component derived automatically into my target design, without the extra step of selecting what to include in derive. I only use configs for CAM fixtures and when I say that I want config "M77" or "M125" I expect always the same fixture object "vise", just with different content inside.

[kgrunawalt]

First use of a configuration version will be slower but we are working to make that faster.
That is a good idea to skip the extra step for selecting. I'll pass it on.

[pierre-yves.monarque]

Hi Itomuta,

We are investigating logs to see why you did hit issues trying to derive from a configured design.

I would have a couple of questions for which answers would help with investigation:
-Are you seeing failed jobs when deriving any configurations from the configured design?
-Are you repeatedly seeing a failed job when trying to derive "M125 raised"?
-Did you see a repair needed UI when opening the configured design (The one defining "M125 raised")
-What is the size of the configured design ? (Average number of components)
-For observed performance issues when deriving, what does slow means, are we talking about seconds? minutes?

Thanks in advance for your time. Any additional information will help with the investigation
Regards

[ltomuta]

---

@pierre-yves.monarque wrote:

-Are you seeing failed jobs when deriving any configurations from the configured design?
-Are you repeatedly seeing a failed job when trying to derive "M125 raised"?

---

This was the first and only time this happened and I've been using the fixture design a lot, but mainly with another configuration. I think this was the first use of "M125 raised" in a while, definitely the first use after a fresh Fusion install, should that mater. I have not had this problem since.

---

-Did you see a repair needed UI when opening the configured design (The one defining "M125 raised")

---

I have opened the file using that link from the error message but there was nothing wrong/different about it. No repair prompt.

---

-What is the size of the configured design ? (Average number of components)

---

These are the stats:

// all componnets, no config applied
With Overrides: LeafOccurrences 33: Bodies 32: VisibleLeafOccurrences 33: VisibleBodies 32: LeafOccurrencesWithVisualMaterialOverrides 0: OccurrencesWithTransformOverides 26

// with "M77 raised" config, my "default" fixture
With Overrides: LeafOccurrences 15: Bodies 15: VisibleLeafOccurrences 15: VisibleBodies 15: LeafOccurrencesWithVisualMaterialOverrides 0: OccurrencesWithTransformOverides 14

// with "M125 raised" config
With Overrides: LeafOccurrences 20: Bodies 20: VisibleLeafOccurrences 20: VisibleBodies 20: LeafOccurrencesWithVisualMaterialOverrides 0: OccurrencesWithTransformOverides 16

---

-For observed performance issues when deriving, what does slow means, are we talking about seconds? minutes?

---

I think I was mostly expressing a feeling, I don't have any measurements to back it up. When loading that M125 it felt slower than when loading the usual M77 but then again I think I'm unhappy with the speed of deriving the M77 as well. 🙂 Maybe the fact that saving it failed was also contributing to the "something was wrong altogether" feeling. But definitely in the seconds range.

Probably I could/should optimize the design, reduce the number of bodies...  

[pierre-yves.monarque]

Thank you Itomuta for your answers. It does help!

We are investigating why this failure was observed and are working on improving performances of first use of a configuration.

Regards

[kth_chowH79GE]

Hi, i am experiencing the same issues where I can't save files with configured designs. Other files without configurations have no issues saving to the cloud. This only recently started happening the last few days, I used to be able to save configured design files before. Here's what I've tried so far:

• I rolled back to a previous version that I was able to save properly. I made a copy of that version and tried saving it, and it failed to save to cloud
• Deleting the q folder and xml file following this
• uninstalling/reinstalling fusion

I've attached diagnostic files if that helps. 

[CGBenner]

@kth_chowH79GE 

Hello and welcome.  You may also want to keep an eye on this current discussion on what appears to be the same issue.

[alex_winter]

I am having the same issue.  What I got to work currently is once I receive that error, I go to the service utility and reset fusion.  Once Fusion is reset I can re-open fusion and navigate to that same design.  When I reopen it, It saves the last session (the one before) and then opens the file we just clicked on.

not really a fix just a tiny workaround and maybe a clue to what is going on.

[karina.harper · Accepted solution]

@kth_chowH79GE 

We had an issue with Configuration save in certain regions today, can you try again? 

Cheers,

Karina

[kth_chowH79GE]

It's working now! Thanks @karina.harper and @CGBenner !