IFTTT Pro vs Free Queue Priority During Platform Congestion

Queue Priority Behavior Under Load

IFTTT's Free tier polls most triggers at a 15-minute minimum interval, while Pro tier reduces this to 1 minute and offers realtime webhooks for supported services. Applet runs are queued and processed sequentially per user, but the platform does not publish an SLA for end-to-end latency. Observed delays range from seconds for realtime delivery to hours when polling backs up under load.

The documentation for service providers specifies a 30-second webhook timeout with exponential-backoff retries, yet it does not define maximum queue depth or any prioritization logic between subscription tiers. During platform-wide congestion, it is unclear whether Pro users' queued runs receive preferential scheduling over Free users, or whether all runs share a single FIFO queue regardless of plan.

Specific Questions

1. Does IFTTT implement tier-aware queue prioritization when the platform experiences high concurrent trigger volumes?
2. If prioritization exists, is it applied per-applet, per-user, or globally across the execution pipeline?
3. Are there measurable latency differences between Free and Pro runs during documented congestion events?