Connections/wires messy and hard to control

[ExploratoriumGPT]

Cross post from Reddit
My workplace uses Draw Io for electrical schematics and the wires often take surprising routes that require tons of rerouting to not block the symbols. Attempts to re-route them require many waypoints and often leads to extra waypoints that are hard to remove.

Is there anyway to get the great perimeter connection point behavior out of points that do not lie on the permitter?
I think the default "direction" of a connection could simply be away from the center, but it seems to have this logic only for points on the edges

Any explanation for crazy routes, like in the 2nd gif?

Environment:

• draw.io version: app.diagrams.net on
• Browser (if web): Brave
• OS: Win 11

I am using
Orthogonal waypoints
Link to diagram example

File download trash.drawio

[draw-io-triage-bot[bot]]

👋 Thank you for opening this issue!

---

Summary: The user reports that draw.io's automatic edge/wire routing produces unexpected and messy paths when connecting to custom connection points that are not on the shape perimeter (common in electrical schematics), and requests that the connector direction logic for interior connection points default to routing away from the shape center, similar to how perimeter connection points behave.

---

📝 Additional Information Needed

To help us investigate this more effectively, could you please provide:

• Environment: Which platform is being used (draw.io desktop, web app, Confluence, etc.)? What browser and OS?
• draw.io version: What version of draw.io is being used?
• Edge/connection style: What edge routing style is being used (orthogonal, Manhattan, etc.)? Are custom connection points defined on the shapes?
• Diagram file: A sample .drawio file demonstrating the issue would help developers reproduce the routing problems, especially the 'crazy routes' shown in the 2nd gif.

We also have some questions:

• Are the electrical schematic symbols custom shapes with custom connection points defined inside the shape boundary (not on the perimeter)?
• What edge/connector style are you using? (Right-click a connector > Edit Style to check — e.g., orthogonal, entityRelation, etc.)
• Could you share a minimal .drawio file that reproduces the unexpected routing behavior shown in the GIFs? This would greatly help in diagnosing the routing algorithm's behavior.
• Have you tried using 'sharp' or 'straight' connector styles instead of the default orthogonal routing to see if they behave more predictably for your use case?

📋 Bug Report Template

**Environment:**
- draw.io version: [e.g., web app / desktop 24.x.x / Confluence plugin]
- Browser (if web): [e.g., Chrome 120, Firefox 121]
- OS: [e.g., Windows 11, macOS 14, Ubuntu 22.04]

**Steps to Reproduce:**
1. Go to ...
2. Click on ...
3. See error

**Expected Behavior:**
What you expected to happen.

**Actual Behavior:**
What actually happened.

**Screenshots/Files:**
If applicable, add screenshots or attach the .drawio file.

---

---

_{🤖 This is an automated response to help with initial triage. A human maintainer will review this issue. If you've provided all the requested information, no further action is needed - we'll get back to you soon!}

[ExploratoriumGPT]

for the lost souls of the internet that find this page, the solution seems to be to ensure your connection points are on the perimeter of the shape.
Connection points that are "inland" will have garbage behavior.