{"section":"known-issues","requestedLocale":"en","requestedSlug":"timeout-in-analytics-query-can-prevent-inventory-log-from-loading","locale":"en","slug":"timeout-in-analytics-query-can-prevent-inventory-log-from-loading","path":"docs/en/known-issues/Logistics/timeout-in-analytics-query-can-prevent-inventory-log-from-loading.md","branch":"main","content":"## Summary\n\n\nIn the inventory UI, the update log sometimes fails to load for specific SKUs, displaying the error message: `There was an error loading the data. Please try again.` The request fails with the exception message: `Request failed with status code 500`, which indicates a timeout in the query to Analytics (where the data is stored). As a result, no log for the SKU is shown in the UI.\n\nThis timeout can occur due to high update volume for the SKU or other factors that can cause the query to exceed the maximum allowed execution time of 40 seconds.\n\n\n#### Simulation\n\n\nDue to the variable being the response time for the query to Analytics, it is not possible to replicate in a concise way.\n\n\n#### Workaround\n\n\nIn some cases, refreshing the page will resolve the issue and allow the inventory log to load correctly."}