Here is an example of my node which relies on AI transition, which has "force classify" turned on. In this case I would expect that it never reaches the "force classify failed", but unfortunately it does and does it quite often. The way I have it set up with this "dispatcher" node makes this feature critical for my entire application... https://cdn.discordapp.com/attachments/1220396414430085130/1220396414593405009/image.png?ex=660ec9bb&is=65fc54bb&hm=1e4544b41ad2ee891ab739bf1826553693b5e6a62d2976662b92fb24ca30d7f0&

hey is it possible to shorten your categories Sometimes when the filter is too long it will be too selective in assigning transitions

You can try to use intents after the force classify fails. Like a second line of defense 😅

I have the same problem. It is a bug as in the logs, the option has been rightly classified, but the path is not chosen