Is your feature request related to a problem? Please describe.
I was investigating Sentry warnings for "Large HTTP Payload", and it turns out this is from useRealtimeRun and useRealtimeRunWithTags hooks when run has a large input/output payload.
Describe the solution you'd like to see
We could optimize and try to send less, but I think it would also be nice to have a hook something like useRealtimeRunStatus that only returns couple of fields (run id and status mostly), because when using it to display a progress bar or to display completion badge, we don't really need to pull the whole payload
Describe alternate solutions
Alternatively add options in the hook arguments to omit payload
Additional information
No response
Is your feature request related to a problem? Please describe.
I was investigating Sentry warnings for
"Large HTTP Payload", and it turns out this is fromuseRealtimeRunanduseRealtimeRunWithTagshooks when run has a large input/output payload.Describe the solution you'd like to see
We could optimize and try to send less, but I think it would also be nice to have a hook something like
useRealtimeRunStatusthat only returns couple of fields (run id andstatusmostly), because when using it to display a progress bar or to display completion badge, we don't really need to pull the whole payloadDescribe alternate solutions
Alternatively add
optionsin the hook arguments to omit payloadAdditional information
No response