Users get 502 when connecting to new cloudflare data center until clear cache

Previously, we had been using Cloudflare for mainly DNS and not using the proxy. 3 weeks ago, we started using the Cloudflare proxies. Everything has been fine and dandy until today. After a deployment, some users get a 502 bad gateway error page from Cloudflare. This only happens on Chrome and if you curl the site, campaigns.summitsync.com the site loads in the terminal. I know it is b/c Chrome has cached the 502 page locally. But…

  1. Is this caused if there is any brief downtime?
    a) if I force a cache purge after deployments is this a brute force solution?
  2. is there are way to tell chrome not to cache Cloudflare error pages?