Redirects not working
If a rule looks correct in the app but isn't behaving as expected when you visit the URL, work through these in order, most issues fall into one of these buckets.
Check it in a private window first
This is the most common false alarm. Browsers cache 301 redirects indefinitely once they've seen one, so if you visit a URL, then change or remove the rule, your own browser may keep sending you to the old destination even though the rule is already fixed for everyone else. Open an incognito/private window, or do a hard refresh (Cmd+Shift+R / Ctrl+Shift+R), before assuming the rule itself is broken.
Confirm the domain is Connected
Redirects only fire on domains with a Connected status. If a domain is still Pending or Not Configured, visitors hit a "site not found" page instead of your redirect, even if the rules themselves are set up correctly in the app. Check Domain Statuses and finish DNS setup if needed.
Check your www and bare domain both have DNS set up
If only the bare domain (or only www) has its DNS records in place, traffic to the other one fails at the DNS level before it ever reaches Redirect Supply, it'll look like the redirect "isn't working" when really that version of the domain was never connected. Double check both are covered, see DNS Setup Guide.
Check what's actually being matched
A few things can make a rule silently not match what you expect: query strings are part of the match, so a rule for /page won't catch /page?utm_source=email. Trailing slashes matter too, /page and /page/ are different. And if you're using a wildcard prefix rule (like /blog/*) but the destination URL doesn't include a *, every match will redirect to that one static destination rather than carrying the path over.
Full details: Path Redirects.
Give it a moment
Changes usually take effect within a few seconds. In rare cases it can take up to about a minute for a change to reach every edge location. If a redirect still isn't behaving correctly after a minute or so, it's not a caching delay, something else on this list is the actual cause.
Still not working
Email support@redirect.supply with the domain and the exact URL you're testing, that's usually enough for us to spot what's going on.