Inventory Snapshot Stuck

GraphQL API
1

Help! Snapshot id ‘681a2d83126c24d9558e4dfa’ has been stuck for over a month. Even the abort api command doesn’t work on it.

Can you pls:

  1. Abort it urgently
  2. Put some measures in place where a single snapshot can’t clog up like this for more than say 6 hours?
2

1. Abort it urgently
Pls.

3

Hi Raj, please provide the account_id or email associated with your primary account so that I can resolve this for you. In the future if you have a stuck snapshot please reach out to support@shiphero.com or submit a ticket through our help portal to receive expedient support on the issue.

4

Hi Nathan, the email is rajat@shipbots.com
And noted, I’ll go through that channel next time it happens - thank you

5

Thanks Raj, the snapshot should be cleared now

1 Like
6

YES - Thank you Nathan, it’s sorted now.

  1. Put some measures in place where a single snapshot can’t clog up like this for more than say 6 hours?

Any chance this could be implemented?

7

We have a engineering ticket open to find the root cause issue of the stuck snapshots. Due to the nature of the issue it’s unlikely that will be the exact solution, but we are working to resolve the issue. We have noticed that snapshots with particularly large payloads are getting stuck more commonly. Our recommendation is to use as many filtering variables as you can and still receive the data you need to ensure the snapshots run smoothly.

1 Like