`Unexpected Error` when doing an `update_order` mutation

GraphQL API
1

Hi,

I started getting an Unexpected Error when I try to update an order address.

This is my graphQL query:

mutation {
  order_update(data: {order_id: "T3JkZXI6MzU0MTY2Mjg2", shipping_address: {address1: "123 test address", address2: "", city: "Montreal", state: "QC", zip: "1H1 1H1", country: "CA"}}) {
    request_id
    complexity
    order {
      id
      legacy_id
      order_number
      partner_order_id
      shop_name
      fulfillment_status
      order_date
      total_tax
      subtotal
      total_discounts
      total_price
      box_name
      ready_to_ship
      auto_print_return_label
      custom_invoice_url
      account_id
      updated_at
      email
      profile
      gift_note
      packing_note
      required_ship_date
      tags
      flagged
      saturday_delivery
      ignore_address_validation_errors
      skip_address_validation
      priority_flag
      allocation_priority
      source
      gift_invoice
      allow_partial
      require_signature
      adult_signature_required
      alcohol
      expected_weight_in_oz
      insurance
      insurance_amount
      currency
      has_dry_ice
      allow_split
      hold_until_date
      incoterms
      tax_id
      tax_type
      dry_ice_weight_in_lbs
      ftr_exemption
      address_is_business
    }
  }
}

This is what the API returns:

{'errors': [{'message': 'Unexpected Error', 'operation': 'order_update', 'field': 'order_update', 'request_id': '644b1479e08e0f5b121ebe10', 'code': 22}], 'data': {'order_update': None}, 'extensions': {'throttling': {'estimated_complexity': 10, 'cost': 10, 'cost_detail': {'order_update': {'items_count': 0, 'cost': 10, 'total_cost': 10, 'fields': {}}}, 'user_quota': {'credits_remaining': 2002, 'max_available': 2002, 'increment_rate': 30}}}}

Any idea what I’m doing wrong? Also, this was working yesterday…

2

Hey @hansdaigle,

Thanks for reaching out!
Looking into this issue now, I’ll have an update shortly.

Best,
RayanP

1 Like
3

Any update?

This was working 2 days ago, did Shiphero release any breaking changes to the API yesterday?

Thank you,

4

Hey @hansdaigle,

Thanks for hanging in there!

I’ve gone ahead and continued this discussion on the ticket that was made for this issue. But for transparency, and in case anyone else has run into this issue, we currently have an Engineer investigating this issue.

I’ll post an update here as well when the issue has been fixed.

Please let me know if you have any questions or concerns.

Best,
RayanP

1 Like