subscribeToRun() in preview branches does not appear to fire | Trigger.dev | Page 1

#

Hi @calm cliff. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I'm sorry, but the knowledge sources do not explicitly mention any known issues specific to subscribeToRun() not updating in preview branches. The documentation does describe a general known issue with the realtime API: if a run has a large payload or output (stored in object storage instead of the database), realtime subscriptions—including subscribeToRun—may not work as expected. The workaround is to keep payloads and outputs below 128KB when using the realtime API, but this is not documented as being specific to preview branches—it applies generally to the realtime API in Trigger.dev Cloud Realtime known issues.

There is no mention in the documentation of preview branches introducing additional realtime subscription issues or delays. If you are experiencing delayed updates only in preview branches, and your payloads/outputs are below the 128KB threshold, this may be an undocumented or new issue.

If the problem persists and is not related to payload size, I recommend reaching out to the Trigger.dev team via their support channels for further assistance.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@calm cliff Kapa.ai is still learning and improving, please let me know how I did by reacting below.

#subscribeToRun() in preview branches does not appear to fire

If the problem persists and is not related to payload size, I recommend reaching out to the Trigger.dev team via their support channels for further assistance.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: