Flowpane / Docs
In this section

Check scheduling

A scheduled check is a governance check that Flowpane starts automatically for an eligible Site. It rereads public governance resources and records a new result. A manual check is started by an authorised person. A Deep Scan follows links to gather additional page evidence and is started separately.

The first check

Add the Site, verify ownership, and confirm that monitoring is enabled. Use Run all checks for an initial result when you need one immediately. Verification, a waiting indicator and a scheduled time are not completed checks. Open the recorded outcome before using it in a report.

Recurring checks

The current plan intervals are:

Plan Recurring interval
Free Manual checks only
Starter Weekly
Pro Every 24 hours
Scale Every 12 hours
Agency Every 6 hours
Enterprise Every hour, subject to the service arrangement

Review Site settings → Monitoring, the most recent check time and the result. Eligibility, monitoring state and Site reachability affect whether a check can run. Checks may start later than the nominal due time, and a running check can delay another. These intervals are not a guaranteed completion time or a promise of continuous availability monitoring. Confirm account-specific terms with Flowpane.

Manual checks

Editors and Admins can use Run all checks in the Site header, Run checks in the Sites list, or the play action for one artefact. The result identifies the person who started it. Use an on-demand check after a change or before a client review; it does not make Deep Scan recurring or enable automatic report email.

Backoff after failures

Flowpane can delay recurring attempts after unsuccessful checks. If Auto-checks paused appears, inspect the last result, correct access or server problems and run an on-demand check. Contact support if the Site remains paused. A Blocked result means access was prevented, not that the resource was absent.

Checks and notifications

Scheduled checks create observations. Changes compares completed observations and records meaningful transitions, such as a required file becoming missing or blocked, supported text-file content changing, a significant score drop or a recorded problem being restored. The first observation establishes the starting point; a steady result creates no repeated Change or notification.

Eligible Workspace members can receive in-app Changes from scheduled or manual checks. Proactive Changes email is opt-in, category-based and available for paid-plan Sites; Free has manual checks only and no Changes email. A check does not promise a notification or email on every run. Health digests remain unavailable. See Notifications and Notification preferences.

Confirming that monitoring worked

Open Runs and activity, check the start and completion times, trigger and outcome, and read the affected artefact results. Completed means the run finished, not that every finding passed. A failed or blocked observation needs review even if the Site is labelled Active. Use troubleshooting when the latest result is older than expected.

Reading article

Copy manually

Automatic copying is unavailable. The text is selected; use your device’s copy command.