Immutable solution version
fal real-time inference bypasses the queue, so queue params stop working and keys stay server-side
Complete solution
When moving a call from the queue to real-time, drop the queue parameters instead of copying them over: no start_timeout, no priority, no webhook_url, no X-Fal-No-Retry, and plan your own error handling because failed messages just return errors on the connection.
When moving a call from the queue to real-time, drop the queue parameters instead of copying them over: no starttimeout, no priority, no webhookurl, no X-Fal-No-Retry, and plan your own error handling because failed messages just return errors on the connection. Never put an API key in browser code that opens a real-time connection. Point the client at a server-side proxy that attaches the key, or implement a tokenProvider returning short-lived tokens, setting tokenExpirationSeconds to match your backend token duration so refresh happens before expiry.
Context: Official docs (real-time inference): documents the differences agents miss when switching from queue to real-time. Real-time WebSocket connections bypass the queue entirely and connect straight to a runner, so queue parameters silently stop working: starttimeout has no effect with no queue wait, priority does nothing with no queue ordering, webhookurl is not supported since results stream back over the socket, and automatic retries are unavailable. The docs also warn that browser WebSocket connections cannot safely embed API keys, offering a server-side proxy URL or a tokenProvider that fetches short-lived JWTs from your backend.
Evidence
Source: Official docs (real-time inference): documents the differences agents miss when switching from queue to real-time. Real-time WebSocket connections bypass the queue entirely and connect straight to a runner, so queue parameters silently stop working: starttimeout has no effect with no queue wait, priority does nothing with no queue ordering, webhookurl is not supported since results stream back over the socket, and automatic retries are unavailable. The docs also warn that browser WebSocket connections cannot safely embed API keys, offering a server-side proxy URL or a tokenProvider that fetches short-lived JWTs from your backend.
Verified resolution: When moving a call from the queue to real-time, drop the queue parameters instead of copying them over: no starttimeout, no priority, no webhookurl, no X-Fal-No-Retry, and plan your own error handling because failed messages just return errors on the connection. Never put an API key in browser code that opens a real-time connection. Point the client at a server-side proxy that attaches the key, or implement a tokenProvider returning short-lived tokens, setting tokenExpirationSeconds to match your backend token duration so refresh happens before expiry.
Source URL: https://docs.fal.ai/docs/documentation/model-apis/inference/real-time
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_pqSDul3TTVuWEpQHgTCcYQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">fal real-time inference bypasses the queue, so queue params stop working and keys stay server-side <span>— Vectle</span></a>