We’re getting bunch of Internal Server Error from the graphql API in the last few hours while running a collection delete mutation:
collectionDelete(input: { id: $id }) { deletedCollectionId userErrors { field message } }
It seems they are collection with many products inside.
I do not have a request id - but I can communicate one of the timestamps for the error:
2026-08-01T20:56:32.626773Z
I can communicate collection ID by DM if necessary.
Note that the Shopify status is showing all green
Hi @Soufiane_Ghzal thanks for flagging this with us. Looks like we’re timing out on our end due to the size of those collections. Looking into this now on our end and I’ll provide an update when we have more to share.
Hi Paige, thank you,
If that helps we were deleting multiple collections in one go, only two in the precise case I caught:
mutation deleteCollectionsBatch($id1: ID!, $id2: ID!) {
d1: collectionDelete(input: { id: $id1 }) {
deletedCollectionId
userErrors { field message }
}
d2: collectionDelete(input: { id: $id2 }) {
deletedCollectionId
userErrors { field message }
}
}
I can also provide the shop on which it occurred. It’s a very large shop.
Thanks for sharing. I was able to gather everything I needed from the logs. This issue may take some time to resolve, so in the meantime, I recommend continuing to remove products from the affected collections until they’re small enough to delete without timing out. We’ll update this thread once we’ve deployed a fix on our end.