We've seen elevated failure rates trying to make recurring charges after flow rules change, sending the subsequent charge through a different processor than the first one. This is especially a problem for countries where we use DLocal rather than Adyen.
See if we can add some metadata to these API calls instructing Gravy to send the payment through the same processor as originally used.