> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/faqs/codebeamer-faqs/thread-goes-to-sleep-codebeamer.md).

# Slowness is observed in integration when Codebeamer is configured as one of the end systems

### Description

Slowness is observed in integration when codebeamer is configured as one of the end systems.

### Cause

This can occur because of the API throttling configuration in codebeamer. When same codebeamer instance is used by OIM for integration and other users via API or UI simultaneously with high frequency.

### Solution

**Cases:**

**Case 1. When no API throttling is configured explicitly in the Codebeamer instance:**\
**Recommendation:** Increase the API throttling limit by adding explicit API throttling, or else API throttling enforcement can be disabled by setting `"apiThrottling" : false` in the system configuration.\
If no explicit API throttling is configured in Codebeamer, the Codebeamer enforces the API throttling limit of maximum 3 API requests per second and 120 API requests per minute.

**Case 2. When API throttling is configured explicitly in the Codebeamer instance:**\
**Recommendation:** Increase the API throttling limit where the Codebeamer instance is used highly by users other than OIM users, or else API throttling enforcement can be disabled by setting `"apiThrottling" : false` in the system configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opshub.com/v7.237/help-center-index/faqs/codebeamer-faqs/thread-goes-to-sleep-codebeamer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.