Activity operations, counters, and status semantics
Confirm Activity's time window and coverage before using an event count or an absent row as evidence.
Evidence first
Clear ownership
Verified next step
Choose 30 or 90 days and keep the time zone visible
The server validates the browser's time-zone name and falls back to UTC when it is invalid. Day groups, chart points, filters, and the CSV scope line use that same resolved time zone. The selected window is rolling, not a calendar month or billing period.
The timeline is newest first and capped at 100 returned rows
Rows are sorted by start time and grouped by local day. The client initially renders 20 rows and reveals 20 more at a time, but it does not fetch another backend page. If the server or any source is capped, older work can exist outside the returned set.
Read one row as a normalized operational record
| Field | What it means |
|---|---|
| Operation and category | The normalized product action and its owning area. |
| Scope | A safe domain, keyword, project, list, or other label when the source retained one. |
| Started and duration | Source timestamps; duration remains unknown without a completion time. |
| Status | Queued, running, succeeded, partial, failed, or cancelled in the normalized Activity model. |
| Results | Only persisted target, processed, succeeded, and other known safe counters. |
| Initiator | User, schedule, or system according to the source adapter. |
| Support code | A stable problem code when the source recorded one, not raw internal error detail. |
A status describes the operation, not the business outcome
- Queued and running still lack a terminal result.
- Succeeded means the source reached its successful operational path.
- Partial means some useful output can coexist with missing or failed work.
- Failed and cancelled are grouped into the dashboard's failed total.
- The three-step lifecycle is a presentation derived from start, status, and completion time, not a worker trace of every internal phase.
For partial or failed work, follow the investigation steps and retain the original operation details.
Some source rows are deliberately merged
Activity merges records that describe the same customer operation. Position Tracking device runs under one run group become one operation; linked reservations and settled charges can then be combined. Domain comparison snapshots are not counted again as standalone work in the yearly calendar.
Unmatched usage-ledger charges can appear as cost-only rows. They preserve recorded spend without pretending Crawl Foundry could link the charge to a specific operation.
Billing fields are a trace, not an invoice
An expanded row can show reserved, settled, released, or expired billing state, estimated amount, released amount, charge count, and returned actual settled cost. A missing billing object does not prove an upstream action was free.
Activity is not the legal invoice or receipt surface. Use Billing and the payment provider records for financial documents and reconciliation.
Show more expands the returned sample only
The first 20 rows and each Show more step come from the same server response. The source reads are individually bounded by the effective Activity policy, and the combined timeline returns at most 100 rows. Check the count and Coverage panel before concluding that an older event is absent.
CSV exports exactly the current returned timeline subset
The export includes a scope line, then started time, operation, category, scope, status, initiator, duration, support code, and spend when authorized. Structured filters and client search both affect its rows. Formula-like cell prefixes are neutralized, and a capped or filtered export remains a sample rather than a ledger extract.
Example: Exporting failed work for a review
A team lead filters the 30 day timeline to failed and partial operations and exports the result as CSV for the weekly review.
The file starts with a scope line naming window, time zone and filters, so everyone reading it knows it is a filtered sample and not the full history.
Frequently asked questions
What do the Activity statuses mean?
Queued and running have no final result yet. Succeeded means the operation completed its successful path, partial means some output exists alongside missing or failed work, and failed and cancelled count as failures in the dashboard.
How many rows does the timeline show?
The newest 100 operations in the selected window. The page shows 20 at a time; older work can exist outside the returned set, which the Coverage panel makes visible.
What does the CSV export include?
A scope line, then start time, operation, category, scope, status, initiator, duration, support code and spend when you have billing access, for exactly the rows currently returned.