Hi,
I’m experiencing recurring issues when using Jira Cloud through Microsoft Edge, on an enterprise network that is routed through Cloudflare.
409 Conflict Errors
These happen on POST requests related to engage-targeting:
POST https://mySite.atlassian.net/gateway/api/engage-targeting/api/v2/user/messages/jsw-tailored-board-view-onboarding/start
POST https://mySite.atlassian.net/gateway/api/engage-targeting/api/v2/user/messages/command-palette-issue-action-spotlight/start
They are triggered automatically (not by user actions) and appear intermittently. No special Cloudflare rules seem to be interfering.
404 Not Found Errors
These show up on what seem to be valid Jira endpoints:
GET https://mySite.atlassian.net/rest/api/3/mypreferences?key=next-best-task-feature
GET https://mySite.atlassian.net/rest/api/3/user/properties/CROSS_JOIN_NUDGES_YOUR_WORK?accountId=712020:e1682727-...
GET https://mySite.atlassian.net/gateway/api/townsquare/s/f3163xx3.../workspace/existsWithWorkspaceType?cloudId=...
All of them return a 404 from Jira Cloud even though the URLs are valid.
Additional context
- Access is via Microsoft Edge browser.
- Cloudflare is acting as a proxy for the enterprise network.
- I’m an admin user on Jira, and these errors are not tied to a particular action.
- These headers appear in the requests:
{"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}
with the endpoint:
{"url": "https://dz8aopenkvv6s.cloudfront.net"}
- Errors persist even in incognito mode and with cleared cookies/cache.
- Behavior is inconsistent — some sessions fail, others don’t.
Has anyone else experienced this behavior behind Cloudflare? Could it be related to TLS, caching, or specific headers?
Any guidance or documentation is much appreciated.
Thanks in advance.
4o