Hi @GabeTL
When you are dealing with assembly contexts, it means you are dealing with distributed designs, where some designs are used as references in other designs. In such designs, there is the top level assembly which have other designs (child designs) inserted into them for references. Assembly context features are created in the timeline for top level assemblies. The child designs which have the corresponding contexts have them in the browser. There is an important reason for the difference. In the top level assembly, the context is created at a particular point in the design history so it gets added to the timeline. In the child designs, the context bring in some referenced geometry from the parent design and is not timeline based, hence it does not get added to the timeline.
If you want to update the context from the timeline, you just have to open the top level assembly containing those contexts and update from there. But in reality, it does not matter where you update the context from - from the parent (top level assembly) or from the child (referenced designs) through the browser. The effect is the same.
Your suggestion of allowing all out-of-date contexts to by synced from the browser makes sense. I will discuss this with the relevant people.
Hope this answers your question.
Regards
Gautham
Gautham Kattethota
Software Development