Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Constraint Manager / Finding suspects

I have just created chaos. My intention was to vertically move the small 4mm dia circle indicated by the arrow. It was deliberately not fully constrained, because I wanted to move it to it's final position after defining the adjacent geometry. When I was ready, I moved it a bit, and in the moment I released the mouse button, it snapped to something random. I cannot say what snapped to what, but the whole sketch went overconstrained the very moment.
Now I need to find out what it was. I must say, though, that the constraint manager is of no help in this case. There are constraints turned red that have nothing to do with the entity I moved. Still, everything is red. What I need is a tool that helps me find the offending constraint(s) in a targeted way that lets me narrow in on the most likely ones, maybe a little bit like transparency adjustment works: Show those that have only one step, two steps, three steps … away from my troublemaker. Is there such a functionality somewhere?
Else, I could only delete them all and start over, it appears, or undo (at least until my session timed out, which it now has …), but that would still not let me know what is really going on. This is just a stupid sample case, I write this to demonstrate that the constraint management needs to have more user supportive options, because hunting down overconstrained elements is quite a common thing, and it is always pretty time consuming.
Comments
I think a "simple" ordering by "time created" would help a lot for something like this. Presumably the last couple of relations you added are likely causing the issue so if you could sort them that way it should help in a lot of cases.
In this specific case though, it seems like you should be able to break up the sketch in a couple different ones, which would help simplify things and make troubleshooting easier…