# Operate Channels

> Inspect authentication, routing, deliveries, alarms, and resulting Runs for a deployed Channel.

## Before you begin {#before-you-begin}

Request `channel:read` to inspect deliveries and `channel:manage` for alarms. Keep the AuthProvider, target Agent, and customer-identity model available while troubleshooting. Use canonical CRNs so similarly named resources in other namespaces are not confused.

## Steps {#steps}

1. Verify the Channel CRN, protocol, visibility, and deployed revision.
2. Follow the linked AuthProvider and target Agent references where Console support exists.
3. Inspect recent deliveries for direction, deduplication status, authentication failures, and Run receipts.
4. Retrieve a specific message when payload-level evidence is required.
5. Schedule or cancel alarms only when the deployed Channel declares alarm capability.
6. Follow the resulting Run to inspect pinned authority and durable execution.

## Verify {#verify}

A healthy delivery has authenticated principal evidence, a canonical event id, the expected target Agent, and a durable receipt. Duplicate input should return the recorded outcome rather than creating a second Run. Authentication failures should stop before Channel code executes.

## Next steps {#next-steps}

Read [Run operations](/docs/runs/operate.md) for downstream execution controls or [Agent operations](/docs/agents/operate.md) for target bindings.