Troubleshooting

Start with the affected Site, selected Workspace, observation time and exact visible status. Preserve the explanation before retrying. An old successful result and a failed new attempt are different evidence; neither silently replaces the other.

Site will not verify

Confirm the exact Site address, including the scheme and host. Follow the current verification method and leave its required evidence publicly reachable. Check whether a redirect, password, firewall or cache is serving different content to Flowpane. Verification proves control of the configured Site; it does not certify its governance or establish a CMS connection. See Site verification.

Site blocked or check failed

Blocked means access was prevented; Error means the attempt could not obtain a usable current result. Inspect the returned explanation and public reachability before repeating the check. Ask your host to review the affected request if a challenge or access policy is involved. Do not broadly disable website protection or treat an unavailable score as a pass.

For a queued or running check, allow the existing attempt to finish before starting another. For recurring checks, verify Site eligibility and monitoring state; the plan's interval is not an exact appointment. Check scheduling explains current timing and the absence of scheduled-check customer alerts.

Missing file, Blocked or Error

For example, a missing ads.txt may be appropriate on a Site that does not sell advertising. A missing security.txt invites a decision about a security contact, rather than permission to choose one without the owner’s approval.

robots.txt cannot be read or robots changed

Open the root robots.txt address and compare it with the latest Current observation. Check redirects, public response content and which CMS, plugin or physical file owns it. A change in observation time or output can explain a different finding; saving Proposed text does not itself change the public file. Review intended crawl policy with the Site's maintainer before changing a broad rule.

Sitemap cannot be discovered

Check sitemap declarations in robots.txt and the public sitemap URL. A sitemap index lists child sitemaps; confirm that those files can also be read. Inspect response and XML errors instead of assuming that a reachable homepage proves sitemap availability. See discovery.

If a page is not observed, check crawl completion, limits, depth, links and robots restrictions before removing it from the sitemap. Pages evidence explains what a bounded comparison can establish.

CMS will not connect

Confirm the supported Joomla or WordPress combination, correct installation and Site association, and arranged access. Check HTTPS, the package's visible health and any access restriction with your host. Keep connection secrets out of support messages and screenshots.

Connecting is not Connected; Needs attention requires reading the current explanation. If an action is unavailable after connection, check its specific capability and your role. Connecting Flowpane does not give permission to modify the Site: Managed changes must be explicitly enabled separately.

Recipient remains Awaiting confirmation

Check the address and ask the external recipient to use the confirmation email, including checking their spam folder. An external recipient must confirm personally. Use Resend confirmation where offered if the invitation expired or was missed; resending is not consent. Eligible current member recipients become Active immediately. After removal, unsubscribe or a complaint, follow the displayed restoration or re-consent path rather than repeatedly adding the address. See report recipients.

Report email was not sent

Check plan availability, your sending authority and whether the Site has Active recipients. Queued is still pending. Partly sent requires reviewing each recipient's outcome. Could not send requires reading the failure explanation before retrying. Membership and other eligibility can change between request and send, so a previously Active address can be excluded.

For Sent with no visible email, ask the recipient to check spam, filtering and the address used. Sending success does not prove inbox placement or reading. Sending a report is an explicit action; scheduled checks, notification preferences and inactive digest controls do not schedule report emails. See report delivery.

Site status appears unexpected

Keep Site lifecycle, verification, resource status, CMS connection and recipient status separate. A Site can be Active while an artefact is Missing, or Connected while Managed changes is disabled. Check archiving and restoring if monitoring stopped after a lifecycle change. Restoring a Site does not prove that a new check has completed.

Requesting help

Include the Site URL, affected feature, approximate time and timezone, visible state, and the steps you tried. Share only information you are authorised to disclose. Do not send passwords, tokens, connection secrets or another client's recipient list. Use Support for the appropriate ticket or email route.