Internal error fetching delivery options for subscription contract

Retired Boards Appdev Subscriptions
1

Hey folks,

We are still running into this issue when trying to retrieve the delivery options for a subscription contract. I saw the previous thread:

https://community.shopify.com/c/subscription-apis/graphql-internal-error-fetching-shipping-rates-for-subscription/m-p/1872659#M1561

and contracts for this shop do have a lot of line items but even on the unstable API we are still getting the error. This is preventing us from checking if the contract needs a different delivery method after updating it’s line items.

Here is the query to make the error occur:

query deliveryOptions($id: ID!, $address: MailingAddressInput!) {
    subscriptionDraft(id: $id) {
        deliveryOptions(deliveryAddress: $address) {
            __typename
        }
    }
}

Example X-Request-ID: 00be1eac-432f-4ca6-818d-c7aa36a042c3

1 Like
2

Hi,

Thank you for your report.

We are aware of that problem, and our team is working on a solution.

We’ll update you here once the fix is in place, thank you for your patience!

3

Hello, is this fixed yet?

I am using 2023-04 version and I have replaced all deprecated fields with updated ones as below following the doc.

https://shopify.dev/docs/api/admin-graphql/2023-04/objects/SubscriptionDraft#field-subscriptiondraft-shippingoptions

X-Request-ID: 7f4e541e-6e8c-46c3-8b77-7237a5708ca4

shippingOptions => deliveryOptions

SubscriptionShippingOptionResultSuccess => SubscriptionDeliveryOptionResultSuccess

SubscriptionShippingOptionResultFailure => SubscriptionDeliveryOptionResultFailure

query subscriptionDraft($id: ID!, $address: MailingAddressInput) {
  subscriptionDraft(id: $id) {
    shippingOptions: deliveryOptions(deliveryAddress: $address) {
        __typename
        ... on SubscriptionDeliveryOptionResultSuccess {
          shippingOptions: deliveryOptions {
            ... on SubscriptionShippingOption {
              title
              price {
                amount
                currencyCode
              }
            }
          }
        }
        ... on SubscriptionDeliveryOptionResultFailure {
          message
        }
      }
    }
  }

But I am still getting deprecation warning.

Is this expected?

Looking forward to getting the answer.

Thanks!

4

Hi Craigstra,

A fix has been deployed for this issue that should resolve it. Please test and confirm all is working as expected.

1 Like