Data and RecoverySolve common editing problems

Solve common editing problems

Choose a safe next step without changing site setup or losing work.

Before you start

Choose a safe next step without changing site setup or losing work.

You need

Your agency contact and the site name, editing tool, and exact message shown. Do not send passwords or private customer records.

Steps

Confirm the account and site

Confirm the account, selected site, and environment before changing anything.

Find the matching problem

Find the matching problem below and try its safe action.

Report persistent problems

If the problem persists, report the site, page or item address, tool, time, what you expected, and the exact error. Use a private channel for any sensitive information.

Avoid repeated actions

Do not repeatedly save, approve, upload, resend, or delete while the result is uncertain.

Expected result: Either the issue is resolved safely, or your agency has enough information to investigate.

Common problems

ProblemSafe action
No sites, wrong sites or “No sites found.”Clear Filter sites..., check the assigned account email, and ask your agency to confirm access. Do not create or import a replacement site.
A menu or tool is missingExpand the sidebar or section. Ask whether your site uses that module and whether your permissions include it. Do not alter site settings to make it appear.
Permission deniedStop and ask the agency or business owner to check access. A client member cannot assume owner privileges.
A page or post is missing from a listClear search, status, and category filters, check the site, and inspect another list page if necessary. Do not create a duplicate.
Unsaved changes or a failed saveStay in the editor, read the error, and preserve your intended text privately. Wait for success before navigating. Reloading can discard local changes.
Visual Save is disabled or a dynamic-content warning appearsAsk the agency to identify the source content. Do not remove protected content or switch to code to bypass the safeguard.
AI request limit reachedRead the credit or daily panel and message. Monthly site credits are separate from rolling daily token and hourly request limits. A retry time is not a guaranteed success time. Contact your agency if blocked.
AI proposal cannot be approvedAnother edit may have made it outdated, or it may already be decided. Request a fresh proposal; do not try to force an old one.
Preview failsUse Refresh preview or Try again. Confirm the page, site, and saved result. Avoid submitting forms as a loading test.
Old image is still visibleRefresh preview and check the selected file. Ask the agency about shared image use or caching rather than deleting or uploading repeatedly.
Edit is not on the live websiteConfirm whether you saved in Development. Ask your agency whether publication is complete; Enabled, Published blog status, and AI approval are not proof of transfer to Live.
Live save or auto-save changed something unexpectedlyNotify your agency promptly. Coordinate history recovery instead of making several speculative fixes.
Form record exists but email is missingCheck the correct environment, then ask the agency to investigate email delivery before resending.
Sign-in or security errorUse the secure link supplied by the agency and the configured account method. Try Refresh for a secure-address error; report provider errors. Do not share recovery codes.

Do not assume a loading indicator means failure or a success message means every affected page has been visually checked. Ask your agency before destructive recovery, publication, or access changes.