Log queries and report integrity · FIELD GUIDE
Check dataset capabilities before querying old analytics data
Use the Cloudflare Settings node to distinguish unavailable history, query-window limits and page-size limits.
What the evidence can establish
Cloudflare exposes dataset settings that describe availability and query limits. The documentation distinguishes enabled, availableFields, maxPageSize, maxDuration and notOlderThan. These fields answer different questions: whether a dataset is accessible, which fields are available, how many records a page can return, how wide a query may be and how far back it can read. Treating every limit as a row-count problem can lead to retries that cannot recover unavailable history.
Hypothetical example: a query asks for a long historical interval. Reducing its page size does not address a lookback boundary. Splitting the interval can help with a duration limit only when the requested dates remain available. The diagnostic worksheet should identify which limit is actually exceeded before promising a complete historical report. No particular retention allowance is assumed for your account.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- enabled indicates whether a dataset is available to the requester. Source 1
- c2 · Explanation and verification steps
- availableFields lists fields accessible to the requester. Source 1
- c3 · Explanation and verification steps
- maxPageSize describes a response record limit. Source 1
- c4 · Explanation and verification steps
- notOlderThan describes the readable lookback in seconds. Source 1
- c5 · Explanation and verification steps
- maxDuration describes the width of a requested interval. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- Identify the dataset and whether the query is account-scoped or zone-scoped. Read its Settings node using an already authorized credential with appropriate read access.
- Capture the returned capability fields and retrieval date without saving the credential. Compare the original query against each relevant constraint separately.
- Split a valid interval when duration or page-size limits require it, while retaining stable boundaries. Do not describe data outside the available lookback as zero activity.
- Run one narrow query within the confirmed limits and verify the dataset shape. State the earliest accessible date and any unfilled coverage in the report.
How to check the result
The query scope fits the recorded dataset capabilities. The report distinguishes unavailable history from a successful empty result, and no retry is presented as recovering data beyond the accessible range.
Limits of this conclusion
Capabilities vary by dataset, requester and plan and can change. The saved documentation is not evidence of the limits currently assigned to your account.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-03T23:15:57.082155+00:00
Location: Format / b11; Format / b12; Format / b7; Format / b8; Format / b9
Saved source fingerprint
e0f01caa06397da9cefe7208a5b7ea4972a280d5ee0446dc2294586ad6941793