Yes, I’ve read your thread and even shortly discussed it with Flow. Unfortunately, there’s now idea what it is, but it seems unrelated to Message Carbons.
There’s some IQ-error (feature-not-implemented) routed wrongly (with a extension), which raises the error, which is strange.
I reviewed the changes, which were made since 3.9.3 and can’t imagine, what should cause this error.