When silence deserves
a second look.
Expecting a new report, listing or policy update? Ask PageFluxer to remind you when no change matching your monitor’s rules has been detected for a chosen period.
A reminder, without another monitor
- Create your monitor with the goal, selection and rules you already use.
- In optional setup settings, enable Let me know when an expected update is missing. Or open an existing monitor and find No change alerts under Notifications for this monitor.
- Choose a period from 1 hour to 90 days. Seven days is the starting suggestion.
- Enable at least one delivery method and save. The next successful check starts the observation period.
No change alerts are off by default and included on every plan. Your monitor’s normal check frequency, access, trial and notification allowances still apply. There is no extra capture or AI request.
“No change” follows your alert rules
A matching update is one that qualifies for this monitor’s normal change notifications, even if notifications are turned off. It is not necessarily every raw page edit. With multiple targets, a match on any target restarts the shared period.
| Monitor | What restarts the period? |
|---|---|
| Whole page or selected text | A detected change satisfying your text rule. For an “any change” rule, any accepted text change. |
| Price or availability | A qualifying rule transition, such as the price falling below your threshold. Staying below it does not repeatedly reset the timer. |
| Listings or new entries | A newly detected item satisfying the saved filter. Unrelated entries do not reset it. RSS, Atom and sitemap watches retain their Pro or Business requirement. |
| A readable text update satisfying your saved rule. | |
| Visual monitoring | A change meeting your pixel/area threshold after masks and noise controls. Tiny ignored differences do not reset it. |
For “has this policy received any update?”, use an any-text-change rule. For “has a new senior role appeared?”, use new items with the relevant matching phrase. This is a reminder to review; it does not certify regulatory compliance or prove a page never changed between checks.
Confirmed by a successful check
Saving or previewing a monitor does not backdate the timer. The first successful scheduled or manual check after enabling starts it. A later successful check at or after your chosen period confirms the quiet period. The notification worker then queues a notice.
For example, with hourly checks and a seven-day period, the notice can qualify on the first successful check at least seven days after the starting observation. Worker timing, loading delays, email schedules, quiet hours and retries can delay delivery. A one-hour period on a daily monitor cannot produce a one-hour guarantee.
A matching update starts a new period. Failed captures, pauses, capture/rule/schedule edits and fresh baselines restart observation. A gap longer than two effective check intervals plus ten minutes also starts a fresh period on the next successful check. This keeps expired trials, exhausted check allowances and missed worker runs from being mistaken for verified silence.
We record one logical notice per destination per quiet period. Another successful check on an unchanged page does not send a daily reminder. Turn the setting off and save, then re-enable it to intentionally start a new period.
The monitor details page shows the saved state and observation start. It separates quiet-period notices from capture failures and recovery.
Use your existing destinations
Email follows your effective workspace or custom monitor schedule, including eligible quiet hours and minimum intervals. It arrives as a separate HTML email with a plain-text fallback, not an item in a change digest. Webhooks work with email off. Business Slack and Microsoft Teams use native channel cards and operate independently of email timing.
Each no-change email reserves one shared alert-email allowance when the first send attempt begins; retries reuse that slot. Webhook, Slack and Teams attempts share your existing outbound allowance, including retries. If capacity is exhausted, a quiet-period notice waits and is reconsidered for up to seven days. It expires or is cancelled sooner if the observed period is no longer valid. Ordinary change-email overflow still uses the existing daily digest.
Disabling a destination, changing the endpoint, losing its plan entitlement, pausing the monitor or observing a match cancels a pending notice. With no enabled destination, the quiet period is recorded without sending; save an enabled delivery method to reconsider a still-valid period. A message already in flight cannot be recalled.
See each destination’s result in delivery history. Provider acceptance does not prove inbox arrival. Delivery retries can produce duplicates at endpoints without idempotency; webhook receivers should deduplicate the stable delivery ID. No fake diff, change event, screenshot or AI summary is created for a quiet-period notice.
Works with the API and Chrome extension
Existing extension flows continue unchanged. Open the monitor in PageFluxer to enable no change alerts; no extension update is needed. After AI-assisted setup, choose the optional period yourself.
On plans with API access, include notifications.no_change_minutes in a create or update request. It accepts an integer from 60 to 129600, or null to disable. Omitting the field preserves an existing setting. Normal monitors:write authorization applies.
{
"notifications": {
"no_change_minutes": 10080
}
}The monitor resource includes a no_change status object. Timestamps describe the current observation window. provider_accepted_at means at least one destination accepted it; use delivery history for individual results.
A webhook uses type: monitor.no_change, with a no_change object containing period_minutes, observed_since, confirmed_at, scope: matching_rules and an authenticated monitor link. It has no change object or captured text. Branch on event type before processing it. Signatures and retry IDs use the existing transport.