Troubleshooting

Start with the least destructive recovery step. Preserve useful work before resetting a workspace, revoking credentials, deleting a Doozy, or repeating an external action.

Sign-in doesn’t complete

1. Return to the original browser tab or app after completing sign-in.
2. Confirm cookies and pop-ups are allowed for Doozy and the identity provider.
3. Retry in a regular browser window rather than private browsing.
4. Check that your account is allowed to join the selected organization or workspace.
5. Sign out of Doozy, reopen the app, and sign in again.

If an organization uses SSO, device policy, or domain restrictions, contact its administrator before creating a separate personal account.

Morph is still setting up

New workspaces may need several minutes to prepare their persistent environment. You can configure Doozies while setup continues, but computer, browser, filesystem, and Codex to-dos wait for Morph to become ready.

If setup doesn’t progress:

1. Refresh the workspace status.
2. Confirm the workspace has an active plan and supported region.
3. Retry setup once.
4. Contact support with the workspace ID and timestamp.

Don’t create duplicate workspaces solely to bypass a slow setup unless support recommends it.

Morph can’t be reached

Use this order:

1. Retry the to-do or reopen the live computer view.
2. Restart the affected process or browser session.
3. Restart the Morph environment.
4. Run Recover environment to rebuild services while preserving durable state.
5. Apply an available environment update.
6. Use Reset to snapshot only after preserving recent work.

Recovery and update are designed to preserve durable files and authenticated sessions. Reset can lose recent unsynchronized changes.

A Doozy appears stuck

Open the linked to-do and conversation. Check for:

• an approval or unanswered input request;
• a connected service waiting for authentication;
• a website CAPTCHA or verification step;
• a long-running command with no output;
• another to-do holding a conflicting file or branch;
• a provider limit or temporary outage.

Send a concise redirect if the plan is no longer useful. Cancel only the blocked run when other parallel work should continue.

A website keeps asking for login

Open the live computer view and confirm the correct workspace and account. Complete sign-in through takeover. If the session immediately expires, check provider security policies, cookie restrictions, location rules, or whether another session revoked it.

Prefer a supported connection (aka connector or integration) for recurring work. Don’t ask the Doozy to bypass CAPTCHA, MFA, or anti-automation controls.

A connection won’t install or authenticate

1. Confirm the connection is allowed by organization policy.
2. Verify you’re signing into the intended provider account.
3. Review and accept only the required scopes.
4. Allow the browser to return to Doozy after authorization.
5. Remove the incomplete connection and try once more.

For managed accounts, an administrator may need to approve the app. Include the connection name and provider error when requesting help.

Codex doesn’t connect

For subscription access, complete OpenAI’s browser sign-in and choose the eligible ChatGPT workspace. For API-key access, verify the key belongs to the intended OpenAI Platform project and has available billing.

OpenAI controls plan eligibility, model availability, and usage limits. If sign-in succeeds but Codex remains unavailable, check the selected OpenAI workspace’s permissions and current limits.

Never paste auth.json, access tokens, or API keys into the conversation as a workaround.

An attachment can’t be read

Confirm the file finished uploading and is within the displayed size and format limits. Download it yourself to verify it isn’t empty, corrupted, password-protected, or a link placeholder.

For scanned documents, ask the Doozy to use OCR. For a proprietary format, export to PDF, CSV, plain text, or another supported format while preserving the original.

A schedule didn’t run

Check:

• the schedule (aka routine or timed automation) is enabled;
• the owner Doozy is active;
• the schedule and workspace timezone;
• working-hours restrictions;
• connection and credential status;
• whether an earlier run is still active;
• event filters and deduplication;
• the most recent run record and error.

Run the to-do manually with the same inputs. A manual success followed by a scheduled failure usually points to timing, credentials, or trigger data rather than the skill itself.

An approval is blocked

Open the full approval card rather than the notification preview. If the action is stale or incorrect, reject it and explain what must change. If you can’t approve due to role policy, ask an authorized workspace approver.

Changing a rule doesn’t automatically approve an existing request. Have the Doozy regenerate the action under the new policy when necessary.

Local computer work is refused

Confirm that local execution is enabled for your device and workspace. Review whether the applicable policy is Never allow, Ask every time, or a narrow always-allow rule.

Use Morph unless the to-do genuinely requires local files or applications. Don’t broaden local permissions merely to avoid uploading one specific file.

Update Doozy

The web app updates automatically. Desktop and mobile apps show an update notice when a new version is available. Finish or preserve important local work, install the update, and reopen the affected to-do.

Updating the Doozy app doesn’t reset Morph.

Before contacting support

Include:

• workspace ID and affected Doozy;
• to-do or conversation link;
• approximate time and timezone;
• the operation you expected;
• the visible error and recovery steps already tried;
• screenshots with secrets and personal data removed.

Don’t send passwords, tokens, provider authentication files, full payment details, or unnecessary customer data.

Frequently Asked Questions