> For the complete documentation index, see [llms.txt](https://developer.vario-software.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.vario-software.de/documentation/apps/deprecations-and-usage-findings.md).

# Deprecations and usage findings

Review deprecated calls in the Admin-Center, update your Apps and scripts, and check for new occurrences.

Usage findings help you identify outdated calls in your Apps and scripts. A deprecation finding indicates use of an element marked as deprecated; the finding itself does not stop execution.

## Review findings for your App

Your account needs access to the Developer section and permission to manage the App.

1. Open the **Admin-Center**.
2. Select **Entwickler** and open your App.
3. Find **Auffällige Aufrufe je Stelle**.
4. Set **Art** to **Veraltet** and open an entry to read its full message.

The overview groups findings assigned to your App across tenants. It shows the affected source and element, aggregated occurrences, the number of tenants, and the latest occurrence. Tenant identities are not displayed.

For scripts and integrations without an App assignment, use the installation’s **Auffällige Aufrufe** view with the appropriate permissions. Access requires the **Besitzer** role, or an Admin-Center login with the **Operator** or **Support** role. See [Auffällige Aufrufe in the Admin-Center handbook](https://help.vario-software.de/admin-center-handbuch/installationen-im-uberblick#auffaellige-aufrufe).

## Update and verify

Use the reported element and message to locate the affected call. Check the current [API Reference](https://developer.vario-software.de/api-reference) or [Scripting Reference](https://developer.vario-software.de/scripting-reference) for its replacement and any announced removal information.

After updating your implementation, run the affected workflow again and check for new occurrences. Existing findings may remain visible; use the latest occurrence timestamp to assess whether the call still occurs.

Findings are collected at runtime and reported asynchronously. Counts represent aggregated observations, not failed business transactions or a lifetime call count. An empty overview is not a complete compatibility check.


---

# 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://developer.vario-software.de/documentation/apps/deprecations-and-usage-findings.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.
