I'm experiencing a delay in custom domain propagation on Railway, even though the changes have already been propagated from Cloudflare.

What I did:
Updated DNS records on Cloudflare (A/CNAME pointing correctly).
Confirmed propagation via DNS lookup tools (records are updated).
Flushed DNS cache on my local machine.

Issue:

• Despite these updates, my custom domain isn’t resolving to my Railway-deployed site.

• I’ve waited for a while, but the domain still redirects incorrectly or fails to load.

• Railway panel still shows “Pending” for domain verification.

Questions:
Is there an additional Railway-side caching delay?
Should I manually re-trigger verification or re-add the domain?
Any troubleshooting steps specific to Railway + Cloudflare setup?

Would appreciate any insights! Thanks in advance.