Performance Issues When Using GET /rest/v1/relationships With omitCount=false

Benjamin Lutz
Benjamin Lutz
  • Updated

Published Date: July 2, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect® version(s): All
    • Cloud/CVC
    • Self-hosted
  • Database: MSSQL 2022

IMPORTANT: Access to the REST API and the Jama Connect Cloud MCP Server is restricted to users with a Named Creator Jama Connect license, which includes access to v1, Labs, and SCIM endpoints. Users without a Named Creator license—including those with a Creator Float license—do not have access.

Summary

Frequent calls to the Relationships REST API can cause database lock contention, blocking chains, and broad application slowness—especially when an automation repeatedly requests relationship counts from the following endpoints with omitCount=false (count requested) during high-volume paging/looping:

  • GET /rest/v1/relationships
  • GET /rest/labs/relationships

Requests to these endpoints can execute SQL Server stored procedures

  • sp_get_relationships_for_project_paged
  • sp_get_relationships_for_project_count

which use extremely expensive queries in the backend.

Resolution

Use omitCount=true for Routine Calls

When calling either of these endpoints:

  • GET /rest/v1/relationships
  • GET /rest/labs/relationships

Use:

  • omitCount=true for normal paging/list retrieval
  • omitCount=false only when the total count is truly needed (ideally once per job, not repeatedly per page/iteration)

This reduces calls to the count procedure and helps prevent blocking/deadlocks under concurrency.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.