When a source shows an error status, it means Changeflow encountered a problem while trying to check the page. Here's how to diagnose and resolve common source errors.

Understanding Error Types

Sources can error for several reasons:

  • Page not accessible: The URL is unreachable, deleted, or moved
  • Authentication required: The page requires login or subscription
  • Rate limiting/blocking: The site is blocking automated access
  • Timeout: The page took too long to load
  • Page structure changed: Major site redesign confused the monitoring
  • Invalid URL: The URL is malformed or incorrect

Quick Fix: Try Updating the Source

Often, simply tweakig the prompt and re-saving the source will fix temporary issues.

How to fix:

  1. Go to your Sources page
  2. Click on the errored source
  3. Review the settings (no changes needed)
  4. Click "Save" or "Update Source"
  5. Wait for the next check cycle to see if error clears

This re-initializes the monitoring and can resolve transient errors.

1. Verify the URL is Still Valid

The most common error cause is the URL no longer works.

How to fix:

  1. Copy the source URL
  2. Open it in your browser in a new private/incognito window
  3. Check for:
    • 404 Not Found: Page deleted or moved
    • Redirect: URL moved to a new location
    • Empty page: Content removed or site down

If URL moved:

  • Update the source with the new URL
  • Check if old URL redirects automatically - Changeflow should follow redirects

If page deleted:

  • Delete or pause the source
  • Search for alternative source for same information

If site down temporarily:

  • Wait a few hours and check again
  • Site may be experiencing temporary downtime

2. Check for Authentication Requirements

Some sites require login, subscription, or payment to view content.

How to fix:

  1. Visit the URL in a private browser window (no cookies/login)
  2. See if you're prompted to log in
  3. Check if there's a paywall or membership requirement

If authentication is required:

  • Unfortunately, Changeflow cannot monitor authenticated content by default
  • Contact enterprise support for authenticated monitoring options
  • Consider monitoring a public-facing page instead (press releases, public blog, etc.)
  • Some sites have public RSS feeds as alternatives

3. Site is Blocking Automated Access

Some sites use aggressive bot protection that can block Changeflow.

Signs of blocking:

  • Site works fine in browser but errors in Changeflow
  • CAPTCHA appears when you visit the site
  • Error started suddenly after working previously

How to fix:

  1. Contact Changeflow support - we can enable advanced anti-blocking for your source
  2. Our anti-blocking technology handles most protection (Cloudflare, DataDome, etc.)
  3. Provide the URL and error details for fastest resolution
  4. Success rate for unblocking is over 99.99%

Note: Enterprise plans include priority anti-blocking support with faster response times.

4. Page Load Timeout

Large, slow-loading pages can timeout before fully loading.

How to fix:

  1. Visit the page in your browser - does it load slowly?
  2. Check if page has lots of images, videos, or heavy content
  3. If timeout is the issue:
    • Contact support to increase timeout for this source
    • Consider monitoring a lighter version of the page if available
    • Check if site has mobile version (often faster)

5. Page Structure Changed Drastically

Major website redesigns can confuse monitoring temporarily.

Signs:

  • Source worked fine for months, suddenly errors after site redesign
  • Page loads fine but Changeflow reports errors
  • Content is there but in different format

How to fix:

  1. Delete and recreate the source with current page structure
  2. Update your prompt if the page layout changed significantly
  3. Changeflow's self-healing monitoring should adapt automatically
  4. If it doesn't resolve in 24 hours, contact support

6. Invalid or Malformed URL

The URL itself might have issues.

Common URL problems:

  • Typo in URL: https://exmaple.com instead of https://example.com
  • Missing protocol: example.com instead of https://example.com
  • Special characters not encoded properly
  • Spaces or line breaks in URL
  • URL contains session tokens that expired

How to fix:

  1. Copy the URL directly from your browser address bar
  2. Ensure it starts with https:// or http://
  3. Remove any tracking parameters if possible (usually after ?)
  4. Test the URL works in a private browser window
  5. Update the source with corrected URL

7. Temporary Network or Service Issues

Sometimes errors are temporary on Changeflow's side or the target site's side.

How to fix:

  1. Wait 1-2 hours and check if error persists
  2. Check if you can access the site normally
  3. Try the "Quick Fix" above (re-save the source)
  4. Check Changeflow status page for known issues

If error persists beyond 24 hours:

  • Contact support with source details
  • Errors should self-resolve for transient issues

8. Region or IP Restrictions

Some sites block access from certain countries or IP ranges.

Signs:

  • Site works fine for you locally
  • Error says "not available in your region" or "access denied"
  • Site is known to have geographic restrictions

How to fix:

  • Contact support - we can attempt access from different regions
  • Some content may simply not be accessible due to licensing restrictions
  • Consider alternative sources for the same information

9. Rate Limiting by Target Site

Some sites limit how often they can be accessed by the same user/IP.

Signs:

  • Error mentions "too many requests" or "rate limit"
  • Site asks you to wait before trying again
  • Other sources work fine, just this one errors

How to fix:

  1. Reduce check frequency - change from hourly to daily
  2. Contact support - we can adjust how we access the site
  3. Spread out check times if monitoring multiple pages from same domain

Checking Error Details

To see detailed error information:

  1. Go to your Sources page
  2. Click on the errored source
  3. Look for error message or details
  4. Check "Last Check" timestamp
  5. Review recent history to see when errors started

When to Contact Support

Contact Changeflow support if:

  • Error persists for more than 24 hours after trying these fixes
  • Multiple sources error at the same time
  • Error message is unclear or confusing
  • You need anti-blocking enabled for specific sites
  • Site requires authentication and you have enterprise plan
  • You've tried all troubleshooting steps without success

What to include when contacting support:

  • Source URL
  • Error message or status shown
  • When the error started
  • Whether URL works in your browser
  • Any troubleshooting steps you've already tried
  • Screenshots of error (helpful but not required)

Preventing Future Errors

Best practices:

  • Use stable URLs (avoid URLs with session tokens)
  • Monitor public-facing pages when possible
  • Start with conservative check frequencies (daily) and increase if needed
  • Tag sources so you can quickly identify errors by category
  • Periodically test that sources still work
  • Keep an eye on target sites for announcements of maintenance or redesigns
  • Set up email filters so you notice error notifications quickly

Temporary Solutions

While resolving an error:

Option 1: Monitor alternative URL:

  • Find related page on same site that's accessible
  • Example: If product page errors, monitor category page

Option 2: Monitor third-party coverage:

  • News sites covering the same information
  • Industry blogs or aggregators
  • Social media accounts of the organization

Option 3: RSS feeds:

  • Check if site offers RSS feed as alternative
  • RSS feeds are generally more stable than web pages

Option 4: Pause and retry later:

  • Pause the source to stop error notifications
  • Check back in a week to see if site issues resolved
  • Resume monitoring when site is stable

Common Error Messages and Solutions

"Page not found (404)": → URL changed or deleted - update URL or delete source

"Access denied (403)": → Site blocking or authentication required - contact support

"Connection timeout": → Page loads slowly - contact support to increase timeout

"Too many redirects": → URL redirect chain issue - use final destination URL instead

"SSL certificate error": → Site security certificate issue - usually resolves when site fixes it

"No content found": → Page structure changed or empty - recreate source with updated prompt

Still Having Issues?

If the problem persists after trying these troubleshooting steps, please get in touch at [email protected]. We pride ourselves on quick, expert human support and will work with you to resolve the issue as quickly as possible.