Inbound Routes borked after upgrade to FreePBX 16

[GSnover]

I have noticed this with every machine I have upgraded and then tried to change an Inbound Route - it says the route already exists, and the only way to get around it is to delete the route and then re-create it.

I haven’t done any scratch-loads with 16, so I don’t know if it’s a problem there, but it’s 100% with the upgraded machines. Here is a screenshot:

Existing Route:

But if I try and change anything with it, I get this message - even if I don’t change anything and just re-submit it:

Pretty sure I need to submit a bug-report on this, unless there is a step in the Upgrade-Process that I missed - anyone else seeing this?

[lgaetz (Lorne Gaetz)]

This is resolved in the edge version of the core module

fwconsole ma upgrade core --edge

[GSnover]

Thanks!