to get a personalized navigation.
to get a personalized navigation.
The issue should be fixed now and the GraphQL API should work as before. Nice if you can confirm this, @MagnusHolen and @Sigbjørn Eide.
Thanks, it works now.
Looks good in our end now. Thanks!
Preliminary feedback from our developers:
We will of course continue the work to find a better way of handling this on our side.
We have identified the issue and are working on a solution. We will let you know as soon as we know more.
Hi @MagnusHolen, we have had some issues with GraphQL after deployment this morning, but they should be sorted now. Do you still have problems?
Still problems in our end as well. Not possible to fetch orders/pickinglists which casuses full stop in the warehouse for our customers.
Example traceIds:
00000000000000007cea51e194ac0b52
0000000000000000070e93f2dff68fda
Another example is orgUnit12 in the associate table:
Copyright © 2022 Visma.com. All rights reserved.