Error when requesting carrierService of a subscription contract

Retired Boards Appdev Subscriptions
,

Topic summary

  • Issue: Requesting shippingOption.carrierService fields (e.g., id, name) on a subscriptionContract GraphQL query triggers an INTERNAL_SERVER_ERROR (HTTP 500). Removing carrierService from the selection set returns the expected response.

  • Scope/Replication: The error is consistently reproducible; sample failing request IDs were shared.

  • Cause/Status: The carrierService field is actually deprecated on shippingOption but is not marked as such. The 500 response is acknowledged as a bug rather than intended behavior.

  • Actions/Next steps: A fix is being worked on to prevent the 500 error, and the field description will be updated to clearly indicate deprecation.

  • Guidance/Workarounds: Avoid querying carrierService for now and rely on other shippingOption fields (code, description, title, presentmentTitle) which return successfully.

  • Resolution: Not yet resolved; the thread remains open pending the bug fix and documentation update.

Summarized with AI on January 31. AI used: gpt-5.
1

Every time I request the carrierService.id (or any field on the carreirService) the API returns an INTERNAL_SERVER_ERROR.

Here’s a couple example request ids that failed:

080144a5-9592-4aff-ab9b-e12ce278c661

57818527-2ae3-45f1-906a-80b0b94484d5

It’s been pretty simple to replicate for me.

This causes the error:

query getSubscriptionContract($id: ID!) {
	subscriptionContract(id: $id) {
		deliveryMethod {
			__typename
			... on SubscriptionDeliveryMethodShipping {
				shippingOption {
					carrierService {
						name
						id
					}

					code
					description
					title
					presentmentTitle
				}
			}
		}
	}
}

but if i just remove the carrier service it returns the expected response

2

Hi @Brian_S_1 ! Thanks for sharing this error. I believe carrierService here is actually a deprecated field and should be marked as so. However, the returning 500 does look like a bug, so I’m currently working on a fix for this and will also update the field description to mention the deprecation.

Cheers!

Noah

1 Like