Onde posso abrir um Bug Report para o Logistcs?

VTEX in your native language 🌎 Português
1

Estou fazendo PUT de atualização de estoque no vTex e em alguns deles tomo o seguinte erro:

{ "error": { "code": "1", "message": "A task was canceled.", "exception": { "ClassName": "Vtex.Practices.ServiceModel.Client.Exceptions.InternalServerErrorException", "Message": "A task was canceled.", "Data": null, "InnerException": { "ClassName": "System.Threading.Tasks.TaskCanceledException", "Message": "A task was canceled.", "Data": null, "InnerException": null, "HelpURL": null, "StackTraceString": " at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Vtex.Commerce.Logistics.Common.Availability.<PutItemAvailability>d__14.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Vtex.Commerce.Logistics.Persistence.Inventory.Dynamo.WareHouseItemPersistenceInventoryDynamo.<>c__DisplayClass25.<<SaveWareHouseItemBalanceAsync>b__23>d__27.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Vtex.Commerce.Logistics.Persistence.Inventory.Dynamo.WareHouseItemPersistenceInventoryDynamo.<SaveWareHouseItemBalanceAsync>d__2a.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Vtex.Commerce.Logistics.Persistence.Inventory.Dynamo.WareHouseItemPersistenceInventoryDynamo.<SaveWareHouseItemBalanceAsync>d__1d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n ", "RemoteStackTraceString": null, "RemoteStackIndex": 0, "ExceptionMethod": "8\nThrowForNonSuccess\nmscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\nSystem.Runtime.CompilerServices.TaskAwaiter\nVoid ThrowForNonSuccess(System.Threading.Tasks.Task)", "HResult": -2146233029, "Source": "mscorlib", "WatsonBuckets": null }, "HelpURL": null, "StackTraceString": null, "RemoteStackTraceString": null, "RemoteStackIndex": 0, "ExceptionMethod": null, "HResult": -2146233088, "Source": null, "WatsonBuckets": null } } }

Um dos exemplo de estrutura enviados ao endpoint "http://logistics.vtexcommercestable.com.br/api/logistics/pvt/inventory/skus/{skuId}/warehouses/{warehouseId}?an={accountName}" é:

{ "unlimitedQuantity": false, "dateUtcOnBalanceSystem": null, "quantity": 0 }

Desde já agradeço.

2

Esse JSON que está enviado para o endpoint? Caso sim, está bem errado:

https://documenter.getpostman.com/view/3848/vtex-logistics-api/Hs42#2e41254e-0d48-fcb0-c849-4a76c6ebf390

PUT Update Inventory By Sku and Warehouse

http://logistics.{{environment}}.com.br/api/logistics/pvt/inventory/skus/{{skuId}}/warehouses/{{warehouseId}}?an={{accountName}}

3

Desculpe @Nathan Prestes​ eu colei o JSON errado. Editei a pergunta para corresponder ao valor correto.

Onde o skuId=698 e o warehouseId=10586c3

4

Verificou se este id que mencionou não é o ProductId ao invés do skuId?

5

Sim. Este envio está em um loop que faço somente nos SKUs, e em apenas alguns deles geram problemas. Quando forço o envio dos problemáticos o PUT é corretamente.

6

Acredito que então o caminho seja a abertura de um chamado...deve ser algo pontual nas configurações deste sku que está travando sua integração de funcionar corretamente.