Diagnostics

Dashboard checks

The dashboard reports configured/ready sources, configured/connected targets, enabled profiles, full-baseline readiness, unmatched items, OAuth gateway health, and AniBridge mapping release state. It also surfaces recent runs, latest item activity, managed-list failures, and profile actions.

Refresh mappings updates the AniBridge release independently of the normal dashboard refresh.

Provider testers

Source pages expose connection and discovery actions. Target pages provide a generic API tester with plugin-defined account and search operations. Tester output includes duration and full sanitized result without starting a sync.

Run investigation

For a failed or unexpected run:

1. Record the run ID, profile lifecycle, source, target, and run type.
2. Inspect the fatal error and source/target/core event counts.
3. Filter logs to the last successful provider call and first failure.
4. Expand the affected item for source observations, mapping, captured target state, and planned update.
5. Use the provider tester to confirm credentials and API access.
6. Run a targeted dry-run after correcting settings or manual mapping.

Bulk Revert shows an expandable failed-entry list with source title, diff ID, target instance, feature, and provider error. A provider HTTP 409 commonly means the expected remote version/state no longer matches; inspect the full target snapshot.

Safe logging

Run logs deliberately exclude request query parameters, headers, authorization, cookies, tokens, and bodies. A path such as /api may therefore look generic; provider role, operation, status, timing, and response size identify the request without leaking private payloads.