Hi all,
Wondering if the long wait on application-limit-increase requests is
normal right now, or if I'm in a queue that's stalled.
Timeline:
- April 14 — submitted limit-increase request via developers@strava.com
(App ID 211015, registered webhook subscription 340791)
- May 9 — followed up with diagnostic info: discovered our webhook URL
was sitting behind Cloudflare's Bot Fight Mode, which was challenging
automated probes (including, I suspect, Strava's validation traffic).
Webhook events were silently being blocked.
- May 10 — fixed: routed webhook traffic through a dedicated DNS-only
subdomain (no Cloudflare proxy), TLS via Caddy/Let's Encrypt,
verified reachable. Real activity events are now flowing.
- May 13 — no response yet (29 days total since the original request,
3 business days since the follow-up).
Two questions for the community:
1. Has anyone else had Cloudflare Bot Fight Mode silently block
Strava's automated webhook probes? Curious if this is a known issue
worth documenting so other developers don't hit it.
2. What's the realistic SLA right now on limit-increase requests?
Public docs suggest 5-10 business days but my experience suggests
it's longer.
If a Strava staff member sees this and can either re-trigger the
validation of my webhook URL or share status on the queue, I'd really
appreciate it. Happy to share more context in DMs.
Thanks,
Nitin (FitSethu, coaching platform for Indian fitness businesses)