# Usage troubleshooting

A paused task can result from an allowance limit, unavailable account checks, a provider error, or a background-worker limit. Those cases need different responses. Start with the exact message and the account Usage view.

## An allowance is at 100 percent

Check which window is exhausted and whether a reset time is shown. Accounts can expose several windows; one available meter does not override another exhausted allowance. A rolling window also need not reset at your local midnight.

Wait for the displayed reset or use the account options offered. Do not infer a number of remaining messages from a percentage. Requests differ in length and can involve model work, speech, and other services.

## The trial has time left but work is paused

Time and usage are separate trial limits. The trial allowance can be used before its end date. Read the message that explains when access opens again, and review the checkout terms for when a subscription starts.

On-device dictation is separate from hosted agent work. Test the intended mode rather than assuming an exhausted hosted allowance should disable every local feature. See [Plans and trials](/nock/plans-trials).

## Usage or account status cannot be checked

Messages such as **Could not safely check your usage allowance**, **Could not safely record this call**, or **Could not check your Nock plan** describe a temporary service failure. They do not necessarily mean you have consumed your allowance.

Wait and retry a small request. Avoid repeatedly launching expensive or duplicate tasks. If the error persists, record the time and message for support. Do not delete local history or reconnect every provider to repair a server-side check.

## A worker will not start

Worker concurrency controls how many background tasks may run at once. Review current workers and wait for one to finish, or stop a task you no longer need through its normal controls. This limit is different from usage consumption; an account can have allowance left but no free worker slot.

## A provider rejects the request

Inspect the model or voice service involved. A connection can exist while its credentials are expired, its account has insufficient access, or the service is unavailable. Check [Models and providers](/nock/providers) for connection states.

Adding your own key is only an option where supported by your account and interface. It can create charges with the provider and does not remove Nock's separate availability gates.

## A task stopped after changing something

Before repeating a send, create, or update action, inspect the destination. An external service may have accepted work even when the result did not reach Nock. Continue from the observed state rather than issuing the entire request again blindly.

For a report, include the affected feature, visible allowance/reset information, exact error, time, and whether anything completed. Never include provider keys. See [Support](/nock/support).