Read the explanation beside the action
A blocked action can reflect missing access, incomplete setup, a package limit, stale review or an unavailable provider. These conditions need different remedies.
Start with the visible message and the record it names. Avoid creating duplicate drafts or repeatedly clicking generation while the original task may still be running.
Check in this order
- Confirm the selected organisation and website.
- Check your membership, product access and required permission.
- Review account activation, trial and allowance notices.
- Check the website’s relevant integration or destination.
- Inspect the content’s current saved stage and QA status.
- Check queued or running work before starting another request.
For scheduling, also inspect the local date, website timezone and any linked source dependency. A planned post can be visible on the calendar while still missing content or approval.
Separate platform and website setup
Platform Admin configures API services and application availability. Organisation members link their website-specific accounts and complete content workflows.
If the status says a provider application is missing configuration or access is restricted to a pilot, ask the platform team to review it. Reauthorising your personal account cannot supply the platform’s missing application settings.
Handle uncertain results
A browser timeout can happen after work started. Refresh the saved status and inspect history. For remote publishing, check the destination before retrying an uncertain submission.
When asking for help, provide the website name, record link, time of the issue and the exact visible error. Include the steps that led to it. Leave out passwords, tokens and private customer data.
A useful support report lets someone reproduce or locate the problem without guessing which website, draft or connection you meant.