Copying Merge Nodes Broken?

I don't know if I would technically call this a bug... but I found something that seems to be broken in the workflow in the Fusion Page in Resolve.
If you copy and paste a node tree from one comp to another it is possible to have "broken" Merge nodes. Sometimes because of the way comps are created from clips you can end up with a comp that starts on frame 2500 say... if you copy that into a comp that ends on frame 1000 you cant get that merge node to show up.
The merge node doesn't have the global in and out slider in the inspector tab, so you cant pull it back in from there. If you try to find it in the timeline it is not visible and the spreadsheet seems to have a bug where if you pull a tool too far you can not type in a value to bring it back. If there is animation on the merge you can scroll way over and see that and move it, or use the spread sheet to adjust the timing... but you can not get the actual merge node to show up.
So you are left having to rebuild. It seems like this would be a pretty common thing to do... copy and past parts of a node tree into another comp. but this has caused several broken comps I couldn't figure out for a long time.
If you copy and paste a node tree from one comp to another it is possible to have "broken" Merge nodes. Sometimes because of the way comps are created from clips you can end up with a comp that starts on frame 2500 say... if you copy that into a comp that ends on frame 1000 you cant get that merge node to show up.
The merge node doesn't have the global in and out slider in the inspector tab, so you cant pull it back in from there. If you try to find it in the timeline it is not visible and the spreadsheet seems to have a bug where if you pull a tool too far you can not type in a value to bring it back. If there is animation on the merge you can scroll way over and see that and move it, or use the spread sheet to adjust the timing... but you can not get the actual merge node to show up.
So you are left having to rebuild. It seems like this would be a pretty common thing to do... copy and past parts of a node tree into another comp. but this has caused several broken comps I couldn't figure out for a long time.