> For the complete documentation index, see [llms.txt](https://docs.digma.ai/digma-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digma.ai/digma-developer-guide/use-cases/get-early-feedback-on-bottlenecks-and-code-issues.md).

# Get early feedback on bottlenecks and code issues

### Learn of code-related issues, from multiple environments

As the code gets executed, either in your local environment, in CI staging, or in production - Digma learns about how it performs, scales, and identifies any process issues or anti-patterns that should be dealt with. 

As you work on your code, any newly detected issues will appear in the issues side panel as `unread`. 

<figure><img src="/files/H0o6JbNojfOtJhNgqwVe" alt=""><figcaption></figcaption></figure>

Additionally, the code itself will be highlighted to signify whether any critical issues are present:

<figure><img src="/files/6h9A5kla25PJGzqymyMo" alt=""><figcaption></figcaption></figure>

### Recheck issues after fixing the source problems

Once an issue Digma detected is fixed, you can use the `recheck` option on the issue card. Digma will start re-examining the problem based on new data to determine whether the issue is indeed fixed.  This is not mandatory for detecting whether an issue is fixed but can expedite the detection process.

<figure><img src="/files/IIti5iMHE23ZJuJ5R6Hu" alt=""><figcaption></figcaption></figure>