Troubleshooting

Sign-in returns to the wrong place

Start sign-in from the Experiencer origin you intend to use and allow the Google redirect to finish in the same browser. If the browser blocks the return, close duplicate sign-in tabs and try once from a fresh Experiencer tab. A managed Google account may restrict third-party sign-in.

Do not change bookmarked privacy or terms URLs; /privacy and /terms remain the verified first-party paths.

Cloud status is stale or conflicted

Wait for an in-progress save to complete. If the editor reports offline status, confirm the network is available without repeatedly clicking Save. Download a JSON backup before reloading.

For a stale-version conflict, preserve unsaved content, reload the latest cloud document, compare it with the backup, and then reapply the intended change. Revision history and AI review only see accepted saved versions.

An export fails

• Confirm the résumé renders normally before exporting.
• Remove or replace an unreachable external image or font.
• For PNG, allow the browser to finish rendering every page before copying or downloading.
• For HTML/CSS, keep the exported files together.
• For print/PDF, check the destination, paper size, scale, margins, headers, footers, and background-graphics settings.

If the browser reports a memory problem, close unrelated heavy tabs and retry with a simpler document copy. Keep the original JSON.

PDF text is missing or out of order

Use the plain-text extraction check in ATS readability. Replace image-only text, reduce complex multi-column regions, and move important content earlier in the structure tree. Create a new PDF after each structural change.

A temporary review link does not open

Temporary links expire after 30 minutes and can be revoked sooner. They also stop working when the source document is deleted. Create a new link from the currently saved eligible cloud document and share only that new URL.

A stale-version message during creation means a newer cloud save exists. Reload the document status before generating the snapshot.

An MCP client cannot connect

Confirm the client supports remote MCP connections and browser-based OAuth. Remove an incomplete connection, add the Experiencer endpoint again, complete Google sign-in, and approve the requested scope. A previously read-only grant is not silently upgraded for a later write-capable custom-template workflow; reconnect and review the new permission request.

MCP cannot read local-only or unsaved work. Save the intended cloud document, confirm Pro access is active, and retry. If the client reports that a renderer is busy, wait for the retry guidance instead of repeatedly starting new previews.

Send feedback

While signed in, choose Help → Send feedback. Select the report type and describe what you expected, what happened, and the shortest steps that reproduce it. Browser diagnostics are optional and do not include résumé content. Do not paste credentials, payment-card data, or an entire résumé into feedback.

You can also use the Support link below when the in-app workflow is unavailable.