Some purchase_order queries will get 504 Gateway Time-out

GraphQL API
1

Hi,

For some purchase_orders, we are getting 504 Gateway Time-out. For other purchase_orders, we are able to get a proper response using same query with different ID. Please check and advise on this. Thank you!

Sample query

{
purchase_order(id: “UHVyY2hhc2VPcmRlcjo1OTU1OTg=”) {
request_id
complexity
data {
id
legacy_id
po_number
account_id
warehouse_id
vendor_id
created_at
po_date
date_closed
arrived_at
packing_note
fulfillment_status
po_note
description
partner_order_number
subtotal
discount
total_price
tax
shipping_method
shipping_carrier
shipping_name
shipping_price
tracking_number
pdf
images
payment_method
payment_due_by
payment_note
locking
locked_by_user_id
line_items(first: 1) {
pageInfo {
hasNextPage
endCursor
}
edges {
node {
id
legacy_id
po_id
account_id
warehouse_id
vendor_id
po_number
sku
vendor_sku
product_id
variant_id
quantity
quantity_received
quantity_rejected
price
product_name
option_title
expected_weight_in_lbs
fulfillment_status
sell_ahead
note
partner_line_item_id
barcode
updated_at
created_at
product {
id
}
}
}
}
attachments(first: 1) {
edges {
node {
id
}
}
}
vendor {
id
}
warehouse {
id
}
}
}
}

Response to query

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

Thank you!

2

Hi @jwz!
That PO seems to have an unexisting product on ShipHero.
Is there any chance you could try creating it on ShipHero and seeing if that still times out?
Thanks in advance!
Tom

3

Hi Tom, thanks for your reply!
My team only handles data ingestion from Shiphero so we don’t have insight on creation process. Since we are not able to get the data for these purchase orders, would you be able to confirm if these are all due to the same cause?

PO_ID
UHVyY2hhc2VPcmRlcjo0MTk0MDk=
UHVyY2hhc2VPcmRlcjo1NDMxMDI=
UHVyY2hhc2VPcmRlcjo2NzY1NDQ=
UHVyY2hhc2VPcmRlcjo0MTExNTc=
UHVyY2hhc2VPcmRlcjozMTk5NDA=
UHVyY2hhc2VPcmRlcjozMjg5NzQ=
UHVyY2hhc2VPcmRlcjoyNzUwMjA=
UHVyY2hhc2VPcmRlcjo0MDg4NTM=
UHVyY2hhc2VPcmRlcjo0MDg4NTk=
UHVyY2hhc2VPcmRlcjozODY1NDE=
UHVyY2hhc2VPcmRlcjozNTY2Nzg=
UHVyY2hhc2VPcmRlcjoyODM4MTk=
UHVyY2hhc2VPcmRlcjo0NDIyMTI=
UHVyY2hhc2VPcmRlcjo1OTIxNjg=
UHVyY2hhc2VPcmRlcjo1OTU1OTg=
UHVyY2hhc2VPcmRlcjo1NjA2MzI=
UHVyY2hhc2VPcmRlcjo2MzM1OTU=
UHVyY2hhc2VPcmRlcjo2MzQzNQ==
UHVyY2hhc2VPcmRlcjozMTc1NzM=
UHVyY2hhc2VPcmRlcjozNjU3MDk=
UHVyY2hhc2VPcmRlcjozNjY0ODc=
UHVyY2hhc2VPcmRlcjozMTExMDc=
UHVyY2hhc2VPcmRlcjozNDgxNDA=
UHVyY2hhc2VPcmRlcjo0NDQwNzY=
UHVyY2hhc2VPcmRlcjozNjQ3MTQ=
UHVyY2hhc2VPcmRlcjozNjY1NzQ=
UHVyY2hhc2VPcmRlcjoyOTE3Njk=
UHVyY2hhc2VPcmRlcjozMTk5NDE=
UHVyY2hhc2VPcmRlcjoyODIyNzg=
UHVyY2hhc2VPcmRlcjo0MzA5NzI=
UHVyY2hhc2VPcmRlcjo0NTQwNjU=
UHVyY2hhc2VPcmRlcjoyNzg2NjE=
UHVyY2hhc2VPcmRlcjo1MjY0NQ==
UHVyY2hhc2VPcmRlcjo0MDkzNjc=
UHVyY2hhc2VPcmRlcjo0MTEwODE=
UHVyY2hhc2VPcmRlcjozMTkwNjU=
UHVyY2hhc2VPcmRlcjozMTk1OTg=
UHVyY2hhc2VPcmRlcjozODc3MTM=
UHVyY2hhc2VPcmRlcjozMDQ5ODQ=
UHVyY2hhc2VPcmRlcjozOTczMTE=
UHVyY2hhc2VPcmRlcjo1MDA1MTc=
UHVyY2hhc2VPcmRlcjozMjQxMjE=

Thank you!

4

Hi @jwz
I apologize for the delayed response about this!
Is there any chance you could send us the legacy_id for those POs?
Thanks in advance!
Tom

5

Hi @tomasw
Thanks! Nevermind this one, looks like they are mostly resolved by themselves now.

6

Glad to hear that @jwz!
And I apologize for the inconvenience!

Don’t hesitate to reach out if there is anything else we could help you with
Tom