Profile shows current GDP Cloud usage and queue information for your account. The target scheduler sends healthy interactive work directly to an eligible node when safe capacity exists; queue position and ETA matter only when contention, ordering, policy, or recovery actually requires waiting.
Read hosted usage from the current account state
Use the GDP Cloud area in Profile for the usage values attached to your current entitlement period. It can show resource usage, usage by tool, recent activity, remaining allowance, and plan-limit context when available.
Gateway units are a hosted metering concept around GDP tool traffic through the managed gateway. The current Profile and live plan surfaces are the source for your account's current values; this Help article intentionally does not duplicate numeric quotas.
A usage counter describes hosted metering. It does not count as evidence that a corresponding local patch or command completed successfully.
Understand what a queue state means
GDP Cloud should start eligible interactive work immediately when a healthy, authorized, capability-compatible node has reservable capacity. A visible queue is the fallback when no safe eligible node can start now, repository ordering or serialization requires waiting, quota or security policy throttles work, a user burst needs fairness, or durable recovery must preserve work across a disconnect.
An account-scoped queue snapshot can expose the current job status, position, estimated start, reason, estimated tokens, estimated gateway units, and priority. Position and ETA can change as capacity and earlier work change.
eligible capacity: no healthy compatible node currently has safe reservable capacity for this exact tool and workspace.
repository ordering: earlier work for the same repository should finish first.
database pressure: the service is balancing storage pressure before starting more work.
user burst: several jobs from the same account arrived together and are being scheduled fairly.
manual review: a workflow can wait for an explicit review stage.
Commercial plans can provide quotas, guarantees, or reserved capacity, but they do not create execution authority and should not manufacture queue delay while safe eligible capacity is idle. Security throttling remains independent of plan level.
Separate hosted queue progress from local execution
Queued, running, completed, failed, or cancelled Cloud status describes the hosted job or admission flow being observed. It does not by itself prove that GDP Desktop changed the working tree or that a local verification command passed.
For repository work, continue to use fresh GDP Desktop evidence such as exact incoming/apply state, current Git status or diff, and recorded check runs. If a mutation result is uncertain, reconcile that exact operation before retrying it.
Cloud completion and local material completion can be related steps in one workflow, but they are not interchangeable evidence.
