If you have gathered the basic information needed to understand why some resources are skipped in LDX / LQE, you can proceed with the investigation.

Below, you will find some typical observations, the causes behind those, and how you might want to proceed to get them fixed.

First advice is: make sure you are using the latest release of your OSLC Connect tool.

No message when showing details, too many requests


In the skipped resources list stands a column holding the HTTP Response Code. The corresponding value for the skipped resource is 429.

HTTP error code 429 is a way for a server to tell a client that it is sending Too many requests.

This has been seen mulitple time accompanied by an absence of message when clicking on the Show details link inside LQE / LDX.


This is usually because of one of the following reasons

  • a Jira Administrator has enabled the Rate Limiting feature (available since Jira Data Center 8.6);

  • the Jira architecture includes a reverse proxy, and the reverse proxy administrator has implemented rate limiting rules.

In both cases, the rules are too restrictive to let LDX and LQE properly read through all resources.


When using the integrated Rate Limiting feature, you should consider leveraging the Allowlisting URLs and resources in the Rate Limiting feature documentation to allow calls to /**/rest/oslc/**. If this is too much relaxing of the original strategy, you might prefer reverting to the reverse proxy implementation of the rate limiting feature.

When using the reverse proxy rate limiting, you should be able to leverage the User-Agent advertised by those application. For example, LQE usually looks sends LQE/1.0 when doing a request (always check on your own systems what is available and the corresponding values). This provides with an easy way to avoid filtering the indexer’s calls to your Jira instance.