You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use EventSource to retrieve Batch results, it happens that for quickly executed scripts, e.g. echo Hello World, I am not able to subscribe to events after sending the script and I lose the results for that script.
e.g.
// POST /activity/{activityId}/exec sending `echo Hello World`consteventSource=newEventSource(`${baseUrl}/activity-api/v1/activity/${activityId}/exec/${batchId}`)eventSource.addEventListener("runtime",(event)=>console.log(event));
I don't get any events in this example. When I change the script to sleep 1 && echo "Hello World" the event appears.
There is a time gap between sending the post and the event subscription in which an event with the result of the batch script is emitted and I am not able to capture this event.
Maybe it would be possible to add a parameter so that I could specify, for example, from what time I would like to receive events... afterTimestamp ?
The text was updated successfully, but these errors were encountered:
@prekucki , Can we prioritise this? We're having too many cases where we need top put sleep 2 in front of every command to not loose the first events :(
When I use EventSource to retrieve Batch results, it happens that for quickly executed scripts, e.g.
echo Hello World
, I am not able to subscribe to events after sending the script and I lose the results for that script.e.g.
I don't get any events in this example. When I change the script to
sleep 1 && echo "Hello World"
the event appears.There is a time gap between sending the post and the event subscription in which an event with the result of the batch script is emitted and I am not able to capture this event.
Maybe it would be possible to add a parameter so that I could specify, for example, from what time I would like to receive events...
afterTimestamp
?The text was updated successfully, but these errors were encountered: