Documentation
Visibility
Activity, realtime, and troubleshooting
Find the resource status, latest run, activity trail, provider metadata, and failure context before changing production infrastructure.
Updated Jun 22, 2026
2 min read
What visibility tools do
Activity, provisioning progress, deployment history, status pills, and realtime updates help answer what happened, what is happening, and where to inspect failure context. Start with the resource page where the action began.
Before debugging
- Identify the resource: provider, server, site, domain, certificate, deployment, command, backup, or integration.
- Check the latest status pill and activity entry.
- Open the latest run or detailed log before retrying.
- Confirm queues and realtime services are running when progress should update live.
Typical workflow
- Find the resource status.
- Read the latest activity record.
- Open the newest provisioning, deployment, command, backup, or certificate run.
- Check provider metadata and queue health if the issue involves background work.
- Retry only after the failure context is understood.
Checks before changing infrastructure
- The latest action is not still running.
- Failed jobs have been inspected.
- DNS and SSL failures show the target and challenge state.
- Deployment failures show source-control and script output.
- Provider sync state is fresh enough for the form being used.
Common issues
- A page looks stuck because queue workers are not processing jobs.
- Realtime updates are unavailable, so the activity history becomes the source of truth.
- A failed provider sync leaves forms with stale choices.
- A deployment is retried without fixing the command or credential error shown in the log.