Troubleshoot Righty and collect a support report

You can pick up after a Righty error without accidentally building the same thing twice. First check what it saved, then continue from there or send the details to support.

Righty shows an error while building

1. Copy the exact error and note when it appeared.
2. Keep the conversation open and check its activity and change receipts.
3. Open the flow, question, widget, or other item Righty was working on.
4. Check the saved draft and the project's pending changes.
5. Use the recovery action shown with the error, or tell Righty what is already there before continuing.

Righty can fail before or after an action saves. An interrupted reply doesn't mean nothing changed.

For example, if you're building a routing flow for WorkForge (opens in a new tab), compare its saved branches with the ones you requested before asking Righty to create them again. Don't publish a draft you're unsure about just to see whether the error goes away.

Righty keeps running without a final answer

1. Check the latest message for a question or Needs your OK card.
2. If you'd like to interrupt it, choose Stop.
3. Wait for Stopping after this step… to finish.
4. Check the draft to see what Righty saved.

A progress item doesn't mean the work is complete. Righty may still be reading data, making a change, or waiting for your answer or approval. Stop doesn't undo work it already completed.

Avoid asking for the same change in several conversations while the first is active. Changes made at the same time can also prevent a safe undo.

Undo is missing or won't work

Read the reason Righty gives, then check the current item and whether it's published. If you need to recover an earlier configuration, see version history. A restored version becomes a draft for you to review.

Righty offers undo only for the latest eligible change card. It may be unavailable if the draft changed, saved evidence is missing, something was deleted, a split test started, or another change conflicts with the undo.

Restoring a configuration doesn't reverse updates to your email platform or other external actions. See Righty's undo reference for the limits.

Righty says it changed something, but my site looks the same

Check the saved draft, publication state, page targeting, and visitor conditions. Open the authorized debugger in the affected browser to see what's happening. Then test a normal visit without forced overrides.

The change may still be a draft, or the visitor may not meet its conditions. A campaign can also put a qualifying visitor in holdback, which shows the original page. Check these in the project rather than relying on the chat alone.

I can't see Righty

Confirm that you're signed in to the intended project rather than the public demo. The dock is not shown during onboarding or the expired-trial blocking state. A feature-specific permission or plan requirement can also block the requested action without blocking every Righty conversation.

Enlarge

Righty assistant dock with a new conversation field and suggested project questionsOriginalOriginal

If you're using an external AI assistant and its MCP connection fails, check MCP authorization. That connection is separate from the Righty dock.

I still need help

Choose Help, then Email our team, or email support@rightmessage.com. Include:

• Your project name and the item Righty was working on.
• The conversation reference or enough context to find the thread.
• Your exact request, the error text, and the approximate time with timezone.
• What you expected and what the saved configuration contains now.
• Whether the change is a draft, published, or part of a test that hasn't started or is running.
• The shortest set of steps that produces the problem.
• A screenshot with unrelated identities and sensitive values removed.

If the problem happens on your website, open Debugger menu and choose Copy support report for a text report. Turn on Technical details to make Copy JSON available. Include email is optional. If copying fails, use the selectable text instead.

The report omits profile values and credentials, but can still contain private information. Keep passwords, API tokens, and unrelated contact records out of your report.

A Support case reference means the issue was handed off. It doesn't mean a fix has been deployed or your snippet has been republished.