The problem is that it doesn't work until it's updated. It's not that the channels aren't displayed correctly in the connections window, it's that they're not available for sending... Curiously, they do appear in the Matrix, but they don't work.
We're in a parallel sending workflow where it's not necessary to have the connections window open, since the AuxSends work internally.
The user simply perceives that something isn't working as it should... They have no idea (nor could they possibly imagine) that what's happening is that the connections haven't been updated in a window that you don't have open and that you don't have to for this workflow.
(Even though I had it open, it didn't even occur to me.)
Could a connection update be added to the Matrix "accept" function routine?
PS:
In some cases refreshing the connections window doesn't fix it either.
The only way to fix it is to repeat the process of modifying channels until the correct ones appear in the connections window.
The problem is that it doesn't work until it's updated. It's not that the channels aren't displayed correctly in the connections window, it's that they're not available for sending... Curiously, they do appear in the Matrix, but they don't work.
We're in a parallel sending workflow where it's not necessary to have the connections window open, since the AuxSends work internally.
The user simply perceives that something isn't working as it should... They have no idea (nor could they possibly imagine) that what's happening is that the connections haven't been updated in a window that you don't have open and that you don't have to for this workflow.
(Even though I had it open, it didn't even occur to me.)
Could a connection update be added to the Matrix "accept" function routine?
PS:
In some cases refreshing the connections window doesn't fix it either.
The only way to fix it is to repeat the process of modifying channels until the correct ones appear in the connections window.