Skip to main content

Troubleshoot failed or blocked work

Understand job states, resolve common failures, and send useful details to support.

Rooket tracks work that can take time as a background job. The job status shows whether work is queued, running, completed, failed, or waiting for another action.

Queued or running

Leave the job active while Rooket completes the work. Large research, media, and publishing operations can take longer than local edits.

Waiting for approval

Some work cannot advance until an authorized user reviews or approves it. Open the related article, post, roadmap item, or video and review the available action.

Failed generation

Open the failed item and read the visible failure detail. Correct missing inputs or configuration before retrying. A retry starts tracked work again; it does not hide the prior failure.

Failed publishing

Confirm that the destination is still connected and that the selected account, page, site, or channel is correct. If the provider revoked access, reconnect it before retrying.

Contact support

Send the workspace name, feature, item or job identifier, approximate failure time, and what you expected. Screenshots are useful when they do not expose credentials.

Never send passwords, provider secrets, OAuth tokens, recovery codes, or full private logs.

Did this answer your question?