customerPaymentMethodRepote mutation: throttle errors on a bulk mutation API call?

We are seeing rate limits appear in a bulk mutation API call to customerPaymentMethodRemote. We see a number of failed records stating that the system throttled the request. Originally the rate limits did not apply to bulk operations, has that constraint changed?

Hi @Emre_StayAi

Can you share a requestID for an API call where you’re seeing the operation being throttled?

Unfortunately I do not have the request ID of the most recent operations. I do have the bulk GID though which is 5854838587590. For protection of the merchants, I will refrain from publishing the shop ID.

A response line looks like this:

{
    "__lineNumber": 58,
    "data":
    {
        "customerPaymentMethodRemoteCreate":
        {
            "customerPaymentMethod": null,
            "userErrors":
            [
                {
                    "code": null,
                    "field": null,
                    "message": "Too many requests. Please try again in a few seconds."
                }
            ]
        }
    }
}

input:

{
    "customerId": "gid://shopify/Customer/3063637508189",
    "remoteReference":
    {
        "stripePaymentMethod":
        {
            "customerId": "cus_Hbwo08P1T*****",
            "paymentMethodId": "pm_1H2ivEJkIzP2d48x6x*****"
        }
    }
}

Note nothing is wrong with the input as we were able to get it migrated after a second or third call without needing to change the input (besides pruning the lists down). This is a Stripe example but have seen similar issues with Authorize as well.