Troubleshooting

01Environment setup issues

If sandbox setup does not complete, use the progress bar to see which step is stuck: Queued, Provisioning, Deploying, or Ready.

Status	What it means	What to check
Queued	Your sandbox is waiting to start setup.	Wait a few minutes, then refresh the page. If it stays queued, check whether other sandbox work is already running.
Provisioning	Your sandbox resources are being created.	Wait for setup to continue. If it stays here, retry setup from the sandbox page.
Deploying	Your environment is being configured and started.	Check setup logs for the last completed step, then retry if deployment does not finish.
Ready	Your sandbox is available to use.	Open the sandbox and continue your work. If the environment still does not load, refresh the page and try again.

If the status does not change for an extended period, retry setup and review the sandbox logs for the last visible action.

When you create a property or add its default environment, fix any URL errors before continuing. Property and environment setup now blocks invalid or unsafe URLs and shows the problem directly in the form instead of accepting the value.

Use this checklist when setup fails during property or environment creation:

1. Check the validation message shown on the URL field.
2. Confirm you entered a full site URL, including http:// or https://.
3. Remove unsupported, incomplete, or unsafe values.
4. Save again after you correct the URL.

Problem	What to check	What to do
URL is missing a protocol	The value starts with a domain or path only, such as example.com	Enter the full URL with http:// or https://
URL is malformed	The value includes spaces, invalid characters, or an incomplete host	Correct the URL format and save again
URL is blocked as unsafe	The value uses an unsupported or unsafe scheme	Replace it with a standard web URL

If setup still fails after you correct the URL, refresh the page, reopen the property or environment form, and re-enter the value carefully.

02Reading status indicators

Use the sandbox setup progress bar to understand where setup is blocked before you troubleshoot further.

1. Check the current status in the progress bar.
2. Match the status to the table above.
3. Focus your troubleshooting on that stage before retrying setup.

A sandbox that reaches Ready has finished setup. If you still cannot use it, treat the issue as an access or loading problem rather than a setup delay.

03API sequence issues

If API sequence generation or Doctor stops with a validation error, treat it as a configuration problem instead of a stalled run. Validation failures now appear directly in the generation or troubleshooting flow so you can see what needs attention sooner.

1. Read the validation message shown in the API sequence flow.
2. Identify the step, request, or required input named in the message.
3. Fix the missing or invalid value.
4. Start generation again, or relaunch Doctor and choose the guided fix path.

Use these checks for the most common validation failures:

Problem	What to check	What to do
Missing required input	A required value, parameter, or field is empty	Add the missing value, then rerun generation or Doctor
Invalid request setup	A request method, URL, header, or body is incomplete or malformed	Correct the request details, save your changes, and retry
Sequence step does not match the target flow	One step points to the wrong endpoint or uses the wrong data	Update the step so it matches the intended API flow, then rerun

If generation keeps failing after you fix the reported issue, rerun Doctor to surface the next validation error. Work through the reported items one at a time until the sequence completes.

04Access and organization issues

If you open a run detail or test execution detail page that belongs to another organization, the app now redirects you to switch organizations instead of leaving you at a dead end.

1. Follow the prompt to switch to the correct organization.
2. Confirm the organization change.
3. Reopen the run detail page after the switch completes.

If you still cannot open the page after switching organizations, check that you have access to that organization and that you are using the original link.

05Live updates and streaming

If live updates stop during generation, run troubleshooting, or sandbox activity, wait a moment before retrying. Streaming now reconnects more reliably, but brief interruptions can still delay what you see on the page.

Use this checklist when updates appear stuck:

1. Wait a few seconds to see whether the page reconnects automatically.
2. Refresh the page and confirm whether progress resumes.
3. Return to the same task or run detail page and check whether the latest state appears.
4. Retry the action only if the page stays unchanged after reconnecting and refresh.

If an API sequence generation session resumes after you return to the page, let it finish before starting over. Generation progress now persists across navigation, so leaving and coming back does not always mean the run failed.

06Login fails

• Verify credentials are correct.
• Use the login preview tools to confirm the expected redirects and cookies.

07Crawl misses pages

• Check navigation/auth barriers.
• Ensure the starting URL(s) are reachable for the configured credential.

08Submission and error states

If feedback report submission fails, read the error message in the report flow before retrying. Submission failures now appear directly in the UI instead of failing silently, so you can correct the problem with the current report.

Use this sequence when a feedback report does not submit:

1. Read the error message shown after you click Submit.
2. Confirm required fields are still filled in.
3. Retry the submission once after fixing the reported issue.
4. Refresh the page and recreate the report only if the same error appears again.

Problem	What to check	What to do
Required information is missing	A field in the report is empty or incomplete	Complete the missing field and submit again
Screenshot attachment fails	The screenshot is missing, incomplete, or does not finish uploading	Wait for the attachment to finish, or add the screenshot again before submitting
Temporary submission error	The message suggests the request did not complete	Retry once, then refresh and submit a new report if needed

If the error continues after you retry, copy the visible error message and share it with your team or support along with the time of the failed submission.