Start with the message next to the failed step. A page that cannot be read, an unavailable file and a failed app write each need a different fix.

The side panel does not open

Open Chrome’s Extensions menu and check that Starizon is enabled. On a regular webpage, try its icon or your shortcut. Chrome’s settings pages and other protected browser pages limit what extensions can do.

If you switched profiles, check that the extension is installed in the profile you are using. See Install and sign in.

Sign-in or credits look wrong

Check that the website and the extension use the intended Starizon account. Finish the sign-in flow, return to the panel and reopen the account view.

If subscription verification is unavailable, check your network and try again. A failed verification leaves your plan as it was. For a purchase problem you cannot resolve, email support@starizon.ai with the purchase reference.

A page cannot be read

Open the page and check that its content is visible. Complete any sign-in or site verification yourself, then select the page again with @.

When a task covers several pages, look at which ones succeeded and which failed. Ask Starizon to retry the missing sources, and treat the partial result as covering only the pages it read. If a page holds unsaved work, tell Starizon not to refresh it.

For another page with its own URL, open it or paste the link and ask Starizon to read it. If the content only appears after clicks or input on the website, use Agent S6.

On YouTube or Bilibili, PageChat needs accessible captions or a transcript. For PDFs, it needs readable text. If those are missing, provide the text yourself or attach an image with an image-capable model for a question about a visible page area.

Extracted data is missing rows or has wrong fields

Compare the output with a few entries on the source pages. Name the page range, the columns you expect and how to show missing values. Ask for source URLs and for row counts before and after filtering.

For a list spread across separate page URLs, include each page in the extraction request. If the site needs clicks on Next or Load more, use Agent S6 and check which pages it reached. A preview can be shorter than the downloaded file, so check both before you decide rows are missing.

Keep identifiers with leading zeros as text, and ask Starizon to keep different currencies or units separate. See Extract and process data.

A Command rejects attached materials

Use AI Chat for work that combines extraction, files and saved knowledge. Choose Agent S6 or /agent when it also needs website actions. The separate /extract, /automation, /research and Replay entries accept different inputs; they cannot all use the materials attached to a combined task.

Read the input’s warning, then choose a compatible mode or Command, or remove the unsupported attachments. Your draft stays in the input. To start a report with /research, sign in to Starizon. See Skills and Commands.

Knowledge or Space material is not used

Select the intended document, collection or Space from the @ picker and check that it appears as a reference. If you expect Starizon to search your Knowledge Base more broadly, check the Knowledge Base access setting in the input’s Tools menu.

Open the saved material and confirm that it holds readable text or a saved file. If a Space page gives you outdated information, check its page reading preference. For an updated file, confirm that the new version reached the Space.

A file download is unavailable

Temporary files can expire. If you saved the file to a Space, select that Space and ask Starizon to use the saved copy. Otherwise, upload a downloaded copy or recreate the file from sources you can still reach.

A filename in an old answer may point to a file that no longer exists. See History and files.

An app or MCP tool is missing or fails

Check the connection and confirm that the selected account can access the document or workspace. Then check Apps or MCP in the input’s Tools menu. For MCP, also check that you allowed the tool under Manage tools.

Reauthorize an expired app connection. For MCP, test the connection and refresh the tool list. If a write may have partly succeeded, check the destination before you try again. See Apps and MCP.

A custom model or search request fails

Check the provider settings involved. Model keys, model identifiers and Base URLs are separate from search API keys and endpoints. Send a short model request or run Test in Web Search settings, then read the provider’s error.

Changes apply to new tasks. See Models, API keys and web search.

Automation asks for help or stops

Read the question or confirmation in the conversation. Complete sign-in and verification on the website yourself, then use the task’s continuation controls.

If the page or the task changed, explain the current state before you continue. Before rerunning a task that submits a form, updates an app or creates records, check which actions already went through.

A schedule or monitor did not run or notify

Check that Chrome was running, the device was awake and the task was active. Review Next run, Last run and the late-run recovery window you set.

For a scheduled Agent run, open Run history and select its conversation. It may be waiting for your answer or confirmation, or for a daily or monthly task limit to reset. It also pauses after 10 minutes of active work; use Continue in that conversation within 24 hours if you want it to keep going. Check the task’s saved Model and tools and Materials settings if an account, file or Space is unavailable. Changes to a different chat do not update the scheduled task.

For a monitor, its history tells you whether the page could not be read, the condition did not match or the notification failed. Test the chosen channel on its own, then check that Notify via selects it for this task. Repeat-alert settings may require more matching checks or more time between alerts, even when the condition is met.

See Scheduled tasks, Page monitors and Notifications.

Contact support

Email support@starizon.ai with the extension version, Chrome version, task mode and the error text. Add a short note on what you expected and what happened. A redacted screenshot or a public page that reproduces the issue helps.

Remove API keys, tokens, private documents and sensitive form values first. Hold off on clearing extension data as a first step, since it can delete local history, Knowledge Base content and Spaces.