> This page is for version V3 - Beta (default).
> For other versions, use one of these documentation indexes:
> - V3 - Beta (default): https://docs.authlyx.dev/v3/llms.txt
> - V2 - Legacy: https://docs.authlyx.dev/v2/llms.txt
> - V1 - End of support: https://docs.authlyx.dev/v1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.authlyx.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.authlyx.dev/_mcp/server.

# App logs and retention

> App logs and retention in AuthlyX, with examples and troubleshooting.

## Record an event from your software

MyApp may need to record that a customer completed a task or that a protected operation failed. Send an app log through the SDK or Client API. Use a short message that helps the developer investigate the event.

```mermaid
flowchart LR
    A[Signed-in MyApp app] -->|Send log| B[AuthlyX validates session]
    B --> C[Store within the developer plan's log allowance]
    C --> D[Activity: App Logs]
    B --> E[Forward to selected webhooks when configured]
```

## Storage and forwarding are separate choices

Plus can store up to 5,000 app logs; Elite can store up to 10,000. At the storage limit, older stored entries are replaced as new ones arrive. Do not use app logs as an unlimited archive.

App logs appear under Activity, in the App Logs tab. The developer can delete their app logs. Recent Activity is a different feed of dashboard actions and is not the SDK logging endpoint.

A webhook destination can receive configured log events as well. Sending to a webhook does not require exposing its URL in customer software: the software talks to AuthlyX, and AuthlyX delivers to the configured destination. Use delivery history to investigate webhook failures separately from log creation.

## What should be logged?

A useful message is `Export failed: unsupported image format` with a non-sensitive operation identifier. Avoid passwords, complete license keys, session tokens, private metadata, payment details and whole customer documents. Logs can be read by authorized staff and may be forwarded to external services you configure.

## Test the whole route

Send a test log while signed in. Confirm it appears under the correct application and cannot be read through another account. End the session and attempt another log: the rejected session must not keep adding entries. If forwarding is enabled, check the destination's Deliveries tab and verify the signature at your receiving server.

Current log storage is a paid-plan feature. Handle the API's rejection on unsupported plans; a successful initialization does not grant logging rights.