Troubleshooting a Handoff Page That Does Not Continue Automatically

Troubleshooting a Handoff Page That Does Not Continue Automatically requires identifying whether the problem is in plugin visibility, target eligibility, the short-lived handoff, or the separate frontend session before changing configuration.

Diagnostic procedure

  1. Use Continue to frontend on the handoff page before the token expires.
  2. If manual continuation works, inspect whether browser/content-security/optimization rules are preventing the QCUI JavaScript auto-submit.
  3. Verify qcloginasuser.js loads in the new tab.
  4. Create a fresh handoff after making changes; a used/expired token cannot be retried.

Token rule for this page

The handoff page contains a short-lived one-time token and tries to POST it automatically. If JavaScript fails, Continue to frontend must still be used before that token expires; after expiry, return to Administrator for a new handoff.

Information to preserve

Record whether qcloginasuser.js loaded, whether automatic POST occurred, the configured token lifetime, and whether manual Continue to frontend worked. Exclude the raw token and cookies.

When to escalate

If Troubleshooting a Handoff Page That Does Not Continue Automatically persists after the documented layer is verified, stop creating repeated handoffs and preserve the exact error/context. A private support case should include version/state evidence but never passwords, session cookies, MFA secrets, or raw QCUI tokens.

Community Discussion

Want to compare support workflows, share practical tips, or discuss how you use this QCUI feature? Visit the QC User Impersonation Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.