Ответсообщение недоступно
Using the API — which points at api.amboss.space/graphql, sellerAcceptOrder. Same failure from the classic Magma interface. The new Magma UI worked, and it uses a different endpoint entirely: magma.amboss.tech/graphql, with market.order.seller.accept.
So the broken resolver looks like the legacy one specifically. The error it returns is [code=INTERNAL_SERVER_ERROR] [path=sellerAcceptOrder].
Is the legacy sellerAcceptOrder still the supported path for API sellers, or should we migrate to magma.amboss.tech? If the legacy one is being deprecated, that would be good to know — our automation is built on it.