Lifecycle Query Engine skips resources during indexing

When Lifecycle Query Engine (LQE) doesn't index specific artifacts, the skipped resources are listed on the data provider status administration page. This issue can have various causes, and therefore different troubleshooting actions might be required.


If Lifecycle Query Engine skips data during indexing, a warning message flags the problem on the data providers administration page at http://<Host_name>:<port>/lqe/web/admin/data-sources.
Warning indicates that resources are skipped during indexing
The most common causes for skipped resources are internal server errors, socket timeout, authorization issues, deleted resources.
Authorization problem
LQE can't fetch Quality Management (QM) resources. You configure the data provider permission in the wizard when you add a data provider. To resolve the authorization problem, go to the Data Providers administration page, and click the data provider name. Verify the authentication values. If they are correct, check the Jazz Team Server authentication settings.
Example of an authorization issue
Resources are not found
The message indicates that the resource is not available. Verify the data provider.
Error in the data provider
For internal server errors, the data provider logs help you troubleshoot.
Error occurs when fetching data
This error occurs when LQE fails to fetch Requirements Management (RM) data. If you encounter a Bad Request (400) error, contact your support team.


To resolve this problem:
  1. Get the list of skipped resources.

    On the Data Providers administration page, click the data provider that has skipped resources. On the Skipped Resources tab, view the list of artifacts that were not indexed.

  2. Check the data provider logs, and troubleshoot the problem.

    If you are dealing with a temporary issue, retry the skipped resources.

  3. After you troubleshoot, come back to the Skipped Resources page, and try to get the list of skipped resources again. You can also download or clear the list.
  4. If you are not able to resolve the problem, contact your support team.