Activity

Activity attention and troubleshooting

The current Activity surface does not have a separate notification inbox. Attention is a short triage view over bounded returned data; diagnosis still belongs in the source product.

Evidence first

Separate saved measurements from setup states, estimates, and orientation summaries.

Clear ownership

Use the overview to navigate, then inspect evidence in the feature that owns it.

Verified next step

Turn a signal into an action only after checking scope, freshness, and outcome criteria.

Activity does not currently have a separate notification inbox

The current page has an Attention panel with up to six recent queued, running, partial, failed, or cancelled operations. It is derived from the returned dashboard data. It does not send, acknowledge, dismiss, or retain notifications as a separate system.

Use Attention for triage and Timeline for the returned set

There are no Relevant and All notification tabs in the current Activity surface. Attention is a short triage list; the timeline is the fuller returned operation set. Both inherit source, viewer, time-window, filter, and cap boundaries.

Investigate partial and failed operations in their source

Open the row and record operation, scope, timestamps, status, counters, initiator, billing state, and support code.

Read Coverage to see whether the relevant source or timeline is capped.

Follow the safe destination link, or navigate to the owning product when no exact route is available.

Compare Activity with the source run's live state, detailed counters, output, and retry policy.

Retry only from the owning product and only when its current contract permits it.

Verify the new operation and its product output separately.

A missing row has several possible causes

Wrong workspace, 30-day rather than 90-day window, or a selected calendar day.
Category, status, initiator, or cost filter applied on the server.
Free-text search hiding a returned row while aggregates remain unchanged.
Source read, usage read, contributor profile, or 100-row timeline cap.
Viewer-scoped Action Center work or hidden organization billing data.
A product action that is not among the normalized Activity sources.

Preserve the support code exactly

Copy the code together with workspace, operation, scope, start time, current status, and visible counters. Do not paraphrase it. The code is designed to support diagnosis without exposing raw internal errors.

Separate hidden, partial, and unmatched cost

No money controls means the viewer lacks billing access. An at-least spend label means the usage read was capped. A cost-only row means a settled charge was retained but could not be linked confidently to one normalized operation. None of these states is the same as zero cost.

Treat the yearly calendar as a day index

The calendar uses maintained daily rollups when complete and a bounded live fallback while backfilling. It counts selected source operations by day and deliberately deduplicates some comparison and device-group records. Use the 30-day or 90-day dashboard and source product for row-level diagnosis.

Escalate with a reproducible record

Workspace, browser time zone, selected window, filters, and search text.
Generated date, visible count, capped state, and relevant Coverage rows.
Operation title, category, scope, timestamps, status, counters, and initiator.
Support code and billing state when visible, without sharing confidential tokens.
Expected output and current state in the owning product.

Activity Events & Status Notifications & Troubleshooting