Usage troubleshooting

Start with the exact message and the status in Settings → Usage or your Nock account. A task can pause because a fair-use protection applies, account access could not be checked, a provider refused a request, or a hosted service is temporarily busy. These have different fixes.

A service is temporarily unavailable

Check which feature is affected and follow any retry guidance shown for your account. Nock fair-use protections help keep hosted services available; higher plans provide more room. On-device dictation remains separate from hosted dictation.

Trial access is subject to the same fair-use protections. Check checkout for the trial period and when the paid plan begins. See Plans and trials.

Nock cannot check or record usage

Messages such as Could not safely check your usage, Could not safely record this call, or Could not check your Nock plan indicate that Nock could not confirm account state. They do not by themselves mean a fair-use protection was applied.

Wait briefly and retry one small request. Avoid launching repeated or expensive tasks. If the problem continues, record the time and exact message for Support; do not send a key or access token.

A worker or NockBot will not start

Review active tasks and check that your plan includes the feature. For cloud bots, also check that the cloud service is available. Cloud routine schedules are subject to fair-use protections; see Cloud routines.

A provider rejected a request

Check the provider connection and model selected in Models and providers. A connection may have expired or the provider may have its own account restriction. Add your own key only if your plan and Nock’s settings allow it; your provider may bill you directly.

A task may have completed an external action

If a send, post, create, or update was interrupted, inspect the destination before retrying. A service may have accepted the action even if Nock did not receive the result. Continue from what you can verify rather than repeating the whole request blindly.