unresolved components in a file.

[danieleR9DDN]

after some months I loaded again one file that I found having the 2 external components yellow. I updated the file like usual and save it. After that I opened the file that derived it and appears a message that there was 2 unresolved component and when I tried to update the software crashed. This file started to show the two compoents red and I cannot solve, so I decided to delete it and insert again, all loked good except that I cannot derive the two new external components but I solved in another way. Now it starts again to show the new inserted components like red and it seems that cannot revolve this problem. Also the updated drawing that refer all the files showed some lines of the old version and some of the new, I´ve to change the scale of the views and later put again in the correct scale to solve. More I also lost one file yesterday because fusion wasn´t able to upload to the server after hours. It´s embarassing.

[TrippyLighting]

@jeff_strater @Phil.E this deserves attention!

@danieleR9DDN if you can reproduce the exact steps and share a file (not publicly, but with Autodesk employees, who are bund by NDA agreements)  that would certainly help.

Is there a reason you use derived components instead of linked components?

[hamid.sh.]

I too have encountered problem with derived components loosing reference. Might not be exactly same as OP's, but thought reporting it here helps. Here is a screencast.

I had designed a pair of test earphones. In a new file for the charger I inserted some of the components as derive. After a while I made some minor changes in the original (earphones) file and then found out that I can't update derive in the charger file. Trying to reselect components when editing Derive feature leads to crash. The difference between earphones v56 (milestone, at which I inserted derive) and v57 (after the first change) is only a single Chamfer.

[danieleR9DDN]

More than a real reason, is for testing this functionality: derive permits me to use the same component and make some specific modify in assembly, for example holes for electricity in a specific cabinet or a frame bigger for close the gap with the wall in external cabinets. I can for sure use different method but derive is very powerful and I was testing for some use scenario.

Is not real important to recover the file (is very simple solution) but would be nice to have a functionality that works like expected. I cannot spend one hour to figure out how to show again the problem when the solution requires me 20 minutes. 🙂

[Phil.E]

Thanks.

@danieleR9DDN The two crash reports you sent this week are both for an identified issue switching from manufacture to design workspace with specific data. If you could share the design it would help the developers fix the crash, provided I can use the design to reliably repeat the crash.

@hamid.sh. Your two reports sent this week are for a different problem related to derive. Again, a file and repeating steps will help fix the crash. Only 6 reports have been sent in the last 30 days, so it will really help to get this fixed if we can figure out how to recreate the problem from scratch, because the crash is not as important as derived components losing links. Perhaps you can help.

[danieleR9DDN]

---

@Phil.E wrote:

@danieleR9DDN The two crash reports you sent this week are both for an identified issue switching from manufacture to design workspace with specific data. If you could share the design it would help the developers fix the crash, provided I can use the design to reliably repeat the crash.

I don't remember exactly when I sent the report but I think the crash did happen in DESIGN space, nothing to do with manufacture space.

I just tried to open again the file from home and something weird happen: the file of the single cabinet have an old date an was still the old component (600 mm wide) instead the assembly that derive the file was updated with 500 mm cabinet. I open the file and I tried to change again the width to 500 and update the hinges file that needs to be updated and all seems to go well. Instead the file didn't update the date (I guess that cannot update the file to the server) and when I tried to reload and update again the assembly happens the same issue: unresolved component. If I try to reload the single component now the hinges are red and it start again the mess.

I guess there's some problem that prevent to upload correctly the file to the server and now the software is messing between the online version and the cached file. Hope that the problem is relative only to this file.Does I need to add you to the project or what else?

---

@Phil.E wrote:

And for both of you, have you seen this article about resolving unresolved components?

---

The first indication refer to a feature that is no longer present. The second is obvious that I did, is the first thing. 

sincerily looks like a waste of time. I reinstalled the software at the computer at work yesterday but obviouly didn't solve the problem.

[tyler_henderson]

@danieleR9DDN 

The ability to resolve Unresolved Components is now out of Preview and is part of the standard software.  A tooltip on the unresolved component in the browser should tell you the reason it is unresolved, and the right-click menu contains the command "Resolve Component".  This article may be more help.

Unresolved components can occur if an assembly upload is incomplete, or if some design files are deleted from the cloud, or if the design files are moved to a Project to which you don't have permission to access, or if the Project that contains the design files is archived.

I hope this helps some. Regards.

[danieleR9DDN]

---

@tyler_henderson wrote:

Unresolved components can occur if an assembly upload is incomplete, or if some design files are deleted from the cloud, or if the design files are moved to a Project to which you don't have permission to access, or if the Project that contains the design files is archived.

---

This is clearly a problem that prevent to upload the file to the cloud.

I attach the pictures of 2 last version of the file:

version 5 with 600 mm widthversion 6 modified some days ago

I modified the width of the cabinets to 500 some days ago at work and when I opened at home it was still 600 (but strangely the assembled file was updated to 500). I modified again update the yellow component again at home, change the width to 500 and save it without error message, but as you see the file have still an old date and now the external components are red. It's hard to check, but I guess also the icon is not updated and the cabinet looks still 600 but if I ope the file it is 500.

Is clearly something that prevent the file to correctly save online and mess up with the cache copy in computer.

I understand that the software is complex and price cheap, but it's a work tool and the reliability is a must, more than add new functions. In this case the product is simple and the plan is to produce it manually, I only wonder what would happen if it was a complex project ad I need to produce it with CNC

[danieleR9DDN]

Here we're again. Other project, same problem.

Fusion have some problem to update the assembly file so I tried to clear the cache and now I´m not able to reconnect the external file to the assembly. I don´t know why but fusion say that the component is unresolved because I moved or I deleted, but the file is still there exactly in te same folder, only in a later version than what he remember. This project is very big and complex and I NEED TO SOLVE THIS PROBLEM.

[tyler_henderson]

Hi @danieleR9DDN

I sent you a private message so we can try to figure out this problem.

Regards,

[danieleR9DDN]

Hi, thanks for your help. You´ve a message.

Things are becoming worse day by day, I update the heigth of the cabinet at work and now the model looks fine but the drawing show both the line of the old heigth and the new one.

I really don´t know more what´s happening.

model updateddrawing update

[danieleR9DDN]

I notice also that the file save data is weird:

- I saved at upon 9:00 in the morning

- the browser in fusion don´t update date and picture and show upon 7:00 in morning

- the web brower in Chrome shows 13th April version like the last version

It´s evident that there´s some issue with the file on the server and in cache, but I really have no idea about how to solve.

[danieleR9DDN]

ok, this problem start to exist without the derive function.

It´s 8 files stuck, the day is off and I am tired, have someone any idea how to solve the problem without lost the files? All the files refer to external component and I am scared that if I recover from the backup or cache, it will loose the refer

[hamid.sh.]

---

@Phil.E wrote:

...

@hamid.sh. Your two reports sent this week are for a different problem related to derive. Again, a file and repeating steps will help fix the crash. Only 6 reports have been sent in the last 30 days, so it will really help to get this fixed if we can figure out how to recreate the problem from scratch, because the crash is not as important as derived components losing links. Perhaps you can help.

---

@Phil.E Yes, problem is not the crash itself, but loosing derive link once I try to get any later version. Crash only happens when I initiate Edit Derive Feature and reselect components in referenced file, and after observing this I avoided edit and hence no more crash. Sure, I'd love to help. I can privately share the file(s).

[danieleR9DDN · Accepted solution]

A little update for my problems.

It seems that all my issue was caused by a single problem: I reach the maximum number of connected files in the project that I use like library.

I did not notice the problem until yesterday I tried to copy one file from the library project to a new project instead than open it and save it with name like I'm used to do, and an error appears. "Number of inbound relationships exceeds limit".

In few words, there was too many connections between files, over the limit that FUSION can manage and this caused problem to upload files on the server and from this alot of related problem in various parts of the models and drawings.

I was able to solve (at least temporary) moving some of the more called object from the library project to another new library project, this changed the refer from all other assemblies in other projects to the new library and low the number of inbound relationships and now all semms to work well.

I will need to figure out a new workflow for the future so the problem will not show again, but at least now things are working.

Maybe Tyler will have something to add, correct me or explain better.

Daniele

[tyler_henderson]

@danieleR9DDN 

Yes, it appears that the number of "inbound relationships" to the project was the root of the issues.  This caused your saves/uploads for the assembly and external components to not succeed, but we currently don't have indication of that in the UI.  Also, when you tried opening the assembly from a different computer, the latest versions of the components were not available in the cloud data, so they appeared as "unresolved".

We are actually working on addressing both of these issues. 

There is work in progress to increase the allowable "inbound relationships", and also to add a message to tell you what designs are causing the issue if inbound relationships are exceeded in the future.

We are also adding messaging to tell you when there are saves/uploads that are stuck from some reason, so you can cancel them and try saving/uploading again.

Hopefully this will help others in the future.

[Phil.E · Accepted solution]

Thanks for the offer. If you can please share the files with public links, you can PM these to me.

[TrippyLighting]

This bug has been fixed with the October update!