Short answer: no. This issue is pending with Google. The problem occurs when the incoming email contains an SPF failure message. It seems that any SPF failure, even a soft-fail, causes the add-on to ignore the email, even if the email is otherwise 100% safe. There's apparently no quick fix. As a clunky workaround, you can manually forward the incoming email (eg to a dummy address), and this will allow the add-on to process the thread.
Google apparently considers this to be intentional behaviour, and they aren't planning to fix it (although they plan to add more detail to the error message).
More info here:
https://issuetracker.google.com/issues/112064778