> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Observability of CDN

> Account, Transaction and Resource Statuses, Error Code Directory and Transaction Log.

You can follow a CDN on four levels: the provider account, the provisioning operation, the resource, and the status of the CDN block in the Flow graph. All errors come with machine-readable code, which makes it easy to see what happened and what to do.

> [!NOTE]
>
> For whom: Panel Administrator, SRE. Required rights: Read CDN and Flow.

## Status levels

| Level | Where to watch | What shows |
| - | - | - |
| CDN block | Graph Flow | `applying` / `verifying` / `ready` / `blocked` / `failed` / `draft` + operation ID, delivery domain, code and error text. |

In addition:

* Certificates of inspections (samples) are recorded for each run of verification and become obsolete after 12 hours - the status of "ready" is always based on fresh checks.
* Cloudflare AutoDNS integrations have their own status (`unchecked` / `verified` / `failed`) with the time and message of the latest test.

## Journal of operations

* Cloudflare AutoDNS integration activities (creating, updating, deleting, testing, publishing records – both successes and failures) are recorded in the Panel Operations Journal (audit log).

## Error code directory

The codes below are shown to the operator in the status of the operation and the CDN block.

| Code | What means | What to do |
| - | - | - |
| `CDN_AUTOMATION_NOT_AVAILABLE` | There is no connected account ready for automatic use; either there is more than one CDN block in Flow; or the account does not have the keys /Folder ID. | Connect and check the Yandex Cloud account; leave one CDN block; fill in the credentials. |
| `CDN_BLOCK_ENTRY_NODE_REQUIRED` | CDN block is not connected to exactly one input node. | Correct graph: gateway → CDN block → one input node with a domain. |
| `ORIGIN_DNS_FAILED` | The input node does not have a domain or fails to output the delivery domain. | Assign the node a domain and repeat the application. |
| `ORIGIN_TLS_FAILED` | Preliminary HTTPS verification origin failed: no valid certificate on the node. | Configure valid TLS on the node, then repeat the application. |
| `AUTH_INVALID` | Authentication from the provider with the saved keys failed. | Update your account keys and click **Check the keys.**. |
| `CDN_DOMAIN_SETUP_FAILED` | The account cannot read the DNS zones or no zone covers the node domain. | Give the account access to the DNS (`dns.editor`) and make sure that the node domain area exists with the provider. |
| `CERTIFICATE_ISSUE_FAILED` | Managed TLS Certificate request ended in error. | Check the `certificate-manager.editor` and DNS zone permissions; repeat application. |
| `CERTIFICATE_VALIDATION_PENDING` | Certificate not issued in the allotted waiting time. | Wait and repeat the application; check that DNS certificate validation can pass in the zone. |
| `DNS_RECORD_CONFLICT` | Failed to publish DNS-challenge or CNAME delivery domain. | Find and remove conflicting entries in the zone, then repeat the application. |
| `DNS_PROPAGATION_TIMEOUT` | Record published, but did not become visible on authoritative servers during the wait. | Check zone and delegation; repeat application later. |
| `PROVIDER_SCHEMA_MISMATCH` | The Provider has rejected the creation of an origin group or resource. | Repeat the application; if you repeat the error, contact support. |
| `PROVIDER_OPERATION_TIMEOUT` | The provider never returned CNAME for the delivery domain. | Repeat application later; check the status of the service provider. |
| `CACHE_BYPASS_UNPROVEN` | Repeated validation requests returned the same answers - it is not proven that the CDN does not cache. | Make sure that caching in the resource is turned off; re-application will double-check. |
| `NEEDS_QUALIFICATION` | The provider does not have a qualified adapter or functional tests did not pass; block in the status of `blocked`. | For candidates - use Yandex Cloud or manual mode. For samples - eliminate the cause and repeat the application. |
| `UNKNOWN_MUTATION_RESULT` | Delivery domain lease exists without binding - the state requires verification by the administrator. | Do not recreate the block blindly; disassemble the state manually, if necessary - with support. |
| `ROLLBACK_PARTIAL` | Part of the rollback steps did not occur; the operation is marked as requiring attention. | The answer lists unfinished items - finish them manually, see [ Troubleshooting ](https://docs.axottle.com/en/cdn/troubleshooting.md). |

Account Level Errors and Integrations:

\| Symptom | What does | mean What do | do?
\|---|---|---|
\| Account `permission_limited` | Keys are authenticated, but there are not enough roles (list shown in the panel). | Issue the missing roles and recheck the keys. |
\| Account Deletion → HTTP 409 | The account is referenced by CDN resources. | Archive the account or first uninstall CDN blocks. |
\| Cloudflare: 401/403 | Token void or without Zone.DNS. | Recreate token with the right to edit the DNS zone. |
\| Cloudflare: no record is created, no error is | No integration covers the node domain - design pass. | Add integration with the appropriate root domain. |

## Verification

Related pages: [ Resources and operations Z](https://docs.axottle.com/en/cdn/resources-and-operations.md), [ Troubleshooting ](https://docs.axottle.com/en/cdn/troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.