Ah, ok, I’ll take a look at that scenario. However, my main suggestion still applies: this is an error that should only be able to happen if using “natural” results. If you can use a different result type, you should be able to get around it until we fix the main issue.
Regards,