How to Handle a Timeout Error During PM Analyses?
CodeScene provides an optional integration to Jira, Gitlab Issues, and Azure DevOps.
However, when analyzing larger projects (with a huge number of PM issues), it is possible to get a timeout error. PM tools can be slower to respond to queries in large projects, and the default timeout (30s) for the requests isn't large enough to handle it. In this case, we suggest setting an environment variable, PM_DATA_TIMEOUT_MS, to a larger number, for example, 60000.
Note: the first time running an analysis, the PM data fetching step will probably take more time, depending on the number of issues. On subsequent analysis, there is a cache involved, and only the issues that have been updated since the last analysis will be fetched.
Was this helpful?
More in Project Management (PM) Integration
What Does the 'Map Commit to Pull Requests Issues' Option Do?How to Change the Ticket ID Mapping?Which Information is Retrieved from Jira When PM Integration Is Enabled?Why Are No Issues Fetched After Setting Up the PM Integration in Azure DevOps?Still need help? Ask the team