Auto Route fails and reports an unknown error message
closed
s
simoncat
I tried to autoroute the project but it doesn't even start. There are no visible issues (that i know of) a part from the normal "air wires" which should be used by the autorouter.
The autorouter tries to start and then gives this giant error code, which i can't understand and even the copilot says it's not related to the schematic or wiring of the project.
I sincerely apologize if i fail to categorize correctly the issue, unfortnately the browser is loading translated categories in italian using a default translator and is generating very strange terms, so i decided to go with the PCB EDITOR category.
Gretel Bot
This post was closed due to inactivity.
Gretel Bot
closed
s
simoncat
I managed to finish routing manually, it seems that in the meanwhile you solved the bug of the traces!
s
simoncat
The traces that can't be created are the ones in middle layers, while top and bottom copper wiork. When they are created they disappear and become "invisible". Still they are selectable and their pinpoints are shown, so they can be edited even if non-existent.
That is why the autorouter failed.
s
simoncat
Hello Mihir Chaturvedi, the Autorouting kinda works, but it's still buggy as hell :(
Unfortunately even after spending 5 dollars of copilot credits it could not find a solution in a 4 layer pcb! Interestingly, he can't solve GND lanes (????). It has no sense. Also, i found another bug where traces just disappear after creating them, so i can't even finish to route manually the board!
Mihir Chaturvedi
Hi simoncat, thanks for reporting this issue in detail, and sorry you had to experience this! We have identified the issue and fixed it on our end. Could you please try running Auto Layout on your project again and let us know if it works? Thanks!
s
simoncat
*Message from flux copilot:
It looks like that JSON error is coming from the Auto-Layout engine itself—it’s returning an anomaly code that doesn’t match any of the expected “code” values, so Copilot can’t even deserialize the router’s response. In other words, this is a bug in Flux’s autorouter, not in your schematic or layout.
Here’s how I’d proceed:
Upgrade Flux
Make sure you’re on the latest Flux.ai release. We’ve fixed several autore-route/discriminator issues in recent patches.
Work around the bad auto-route pass
Identify which net(s) you were trying to autoroute when the error appeared.
Manually route those critical connections yourself (or in small groups) to unblock the design.
Report the bug
If updating doesn’t help, please file a bug with these details:
Exact Flux version
The JSON payload you received (so we can pinpoint the bad discriminator)
A minimal project or screenshot showing which nets you tried to autoroute
Once reported, the engineering team can correct the schema and push a hotfix. Let me know which nets are problematic and I can help you route them manually in the meantime.