Skip to content
GoCloud
Menu

GoCloud

Troubleshooting and migration limits

Find the failing step, preserve your draft and collect useful evidence without exposing secrets.

GoRun guides

On this page

Start with the actual failure

  • A page loads but an action fails: capture the action name, time, visible error and request status. Do not share cookies, authorization headers, full signed URLs or private report text.
  • Save conflict: another edit changed the version. Preserve your proposal and compare the current version; repeated blind saves are not a fix.
  • Provider operation is uncertain: check its destination before trying again. A timeout can happen after an external service accepted the request.
  • Site or admin feels slow: distinguish document response, large assets, third-party requests and browser rendering. A healthy server response alone does not prove the full screen is usable.

Access and email problems

  • Activation missing: check the correct address, spam folder and provider delivery result. Resend only within the available limits; expired or used links cannot be reused.
  • Protected page: site-wide policy is checked before page policy. Removing a hosting override does not bypass a site owner’s local restriction.
  • Missing admin item: check your permissions and personal sidebar/dashboard preferences. Restore navigation preferences where appropriate; hiding is not permission revocation.
  • Missing agent result: an external agent may still be waiting to connect. Confirm its key, board grant and current run state rather than assuming execution occurred.

WordPress: verify scope before importing

The currently deployed importer must not be assumed to include every draft, private or future item from authenticated REST. Permissions and source endpoints can limit visibility. Confirm support against the exact installed release and your own source account before relying on an import.

  1. Identify the actual installed release and select the correct source mode. Use credentials with only the access required.
  2. Run discovery and preview first. Compare visible types and counts with WordPress using the same authenticated account.
  3. Review status, dates, authors, taxonomy and media mappings. A preview count or progress percentage alone does not prove full migration.
  4. After import, inspect representative public, draft and private records, featured and inline media, links and permissions.
  5. Stop and investigate authentication failures or unexplained count differences. Do not treat a public-only result as complete authenticated migration.

Preview does not grant extra WordPress permissions. Unsupported plugin features and theme behavior require separate review; importing content does not reproduce arbitrary WordPress code.

Ask for help with a bounded report

Include the route, language, browser, time, installed version and the last successful step. Describe expected versus actual behavior. Share sanitized screenshots and IDs only when appropriate; keep passwords, API keys, activation links and sensitive submissions private.