The call log

Usage → Log lists the latest calls of a service one by one: when, who, over which channel, the result and the duration. This page says what is recorded, what is not, how to filter, and how to use the log to find a problem.

Open it

1. Open the service.
2. Click the tab Usage (Nutzung).
3. In the menu on the left choose Log (Protokoll).

The button Refresh (Aktualisieren) at the top right loads the newest calls. The log is filled for published services; for a draft the tab shows "No usage yet".

What the log shows

The heading says it: "The last 200 calls, kept for 30 days." The table Latest calls (Letzte Aufrufe) has the newest call first.

Before the first call the table says "No calls recorded yet."

Filter the log

Two fields at the top right of the table narrow the list:

• All callers (Alle Aufrufer): choose one caller to see only its calls. The list offers the callers that appear in the log.
• All calls (Alle Aufrufe) or Errors only (Nur Fehler): show every call, or only the refused and failed ones.

With a filter set, the line under the heading says how many calls are shown, for example "3 of 12 calls". When nothing fits it says "No call matches the filter."

The filters work on the calls the log holds, at most the latest 200. In Usage → Overview, a click on a row of Who is calling opens the log with that caller chosen.

Reading the Result column

In the English interface the text is the same one the caller received in "error". In the German interface the log shows a short German reason for the common cases; point at it to read the caller's original text. Other texts are shown as the caller received them.

Long error texts are shortened.

What is recorded and what is not

Recorded for each call:

• the time,
• the channel,
• who called — as a token's or connection's name, never as the token itself,
• whether it worked, and the error text if it did not,
• the duration, and whether the answer came from the cache.

Not recorded:

• Input values. The log does not show what a caller sent.
• Result values. The log does not show what the service answered.
• Token values. A token appears by its name only.

Who is named how

• A token's name — the call carried a valid token of this service.
• An AI connection's name — an AI connected to your account ran the service.
• Web app (Web-App) — a calculation in the service's web app or a web snippet.
• Public (no token) (Öffentlich (ohne Token)) — the call carried no token.
• Invalid token (Ungültiger Token) — the call carried a token that is not a valid token of this service. On a protected service the call was refused and the Result column says why.
• A name with "(revoked)" ((widerrufen)) — the call carried a token you revoked. The name is shown for 30 days after the revocation. Tell that client to switch to a current token.

So the log tells you that a caller sent an invalid value at 10:42, but not which value. To find out, ask the caller for the answer they received; its details name the input and the reason.

More on stored data: Data and privacy.

Which calls appear

• Appear: every call that reached the published service — successful ones and ones refused for their inputs, their token or a failed calculation — on all three channels. Calculations in the web app and in web snippets appear with the channel Web app.
• Each scenario counts: a request that calculates several scenarios at the discovery address is listed as one call per scenario.
• Do not appear: calls answered 404 (the service was not published or the id was wrong) and calls answered 429 (the per-minute limit or the month's calls). See Limit errors.
• Do not appear: tests with the test button in the editor. A test runs on the draft and is not a call.

How long entries stay

The log holds the latest 200 calls. When call 201 arrives, the oldest entry leaves the list. Entries are kept for 30 days. On a busy service the 200 entries can cover only a few minutes; on a quiet one they reach back up to 30 days.

For the numbers of a longer period — calls and errors per day, per channel and per caller — use the usage overview.

Find a problem with the log

1. A caller reports an error. Ask for the time.
2. Open Usage → Log and click Refresh.
3. Choose the caller in the filter, or Errors only. Find the entry by time and read the Result column.
4. Open the article for that text from the table above and pass the fix on to the caller.
5. If the entry is missing, the call did not reach the service: the address was wrong, the service was not published at that moment, or a limit answered 429. See 404: not found or not published.

If many callers show the same error after you changed the service, check whether an input was renamed or made required: see Rename, reorder, remove.

For developers and agents

• Entries: time (ISO, shown in the viewer's time zone), channel (api, ai, app), caller, ok or not, the error text for a failed call (at most 120 characters), the duration in milliseconds when known, and a cache mark.
• Size and age: the latest 200 entries, kept for 30 days.
• Callers: a token of the service by its name; an AI connection by its name; the web app; a call without a token as public, kept apart per channel. A call with a token that is not a valid token of this service is listed as "Invalid token", or by the token's name with "(revoked)" for 30 days after it was revoked.
• The channel says how the call arrived: app for the web app and web snippets, ai for the MCP address and connected AIs, api otherwise. It is independent of tokens.
• The stored error text is always the API's English text; the German reason is a display of the interface.
• The filters work in the browser on the loaded entries.
• The log is available to the owner of the service only.
• The log is not an export and has no download. Keep your own records on the calling side if you need a complete history of requests and values.
• For an agent helping a user: the log shows outcomes, not values. To diagnose a refused call, ask for the full answer the caller received (error, message, details).

FAQ

Where do I find the log of my service's calls?

Open the service, click Usage (Nutzung) and choose Log (Protokoll) in the menu on the left. The newest call is at the top.

How many calls does the log keep?

The last 200 calls, kept for 30 days. Older entries leave the list as new calls arrive.

Can I see the input values of a call?

No. Input and result values are not recorded. The log shows when, who, the channel, the outcome and the duration.

Why is a call missing from the log?

Calls answered 404 or 429 are not listed, and neither are tests in the editor. On a busy service the call may also be older than the latest 200 entries.

What does "cache" mean in the Duration column?

The answer came from a stored result of an earlier call with the same inputs, not from a new calculation. See Caching and performance.

What does "Parameter validation failed" in the log mean?

The caller sent a value with the wrong type, outside the limits or not in the list of allowed values, and got no result. The caller's own answer names the input and the reason; see Input errors.

What does "Invalid token" in the Who column mean?

The call carried a token that is not a valid token of this service: mistyped, or from another service. On a protected service such a call is refused, and the Result column shows why. A token you revoked is named for 30 days, with "(revoked)" after its name.

Can I download or export the log?

The log is shown in the app and has no download. If you need a complete history with values, record the calls on the calling side.

Are my test runs in the editor in the log?

No. A test with the test button runs on the draft and is not a call, so it is neither logged nor counted.

Does the log show the caller's IP address?

No. A log entry consists of the time, the channel, the caller's name, the outcome and the duration.

Can I delete entries from the log?

There is no action for that. Entries leave the log on their own: after 30 days, or earlier when 200 newer calls have arrived.

Are batch scenarios logged one by one?

A request with several scenarios at the discovery address is listed as one entry per scenario, and each counts as a call. See Batch calls.