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
{{ message }}
Repository navigation
Commit 909567c
Browse filesBrowse the repository at this point in the historyBrowse files
Keep an open task card current under load, and send a parked message once the Bot is free (#1721)
* Send a parked message once the Bot is free, when the drain found it still working
A message typed while the conversation read busy is parked and goes when the turn is over. The screen reads the turn over a render behind the agent: a drain started while the agent still had a run under way was refused before it asked the server anything, taken for a failed run and held until the person started a turn themselves. The message sat in the thread and never ran, with nothing said (seen once in a task's thread, a steer typed just after the task finished). The refusal is now its own error, and a drain refused for it goes again shortly until the Bot is free. A drain the server failed still waits for a turn the person starts.
* Read only a conversation's own task cards when its work changes, and let a read under way finish
Every work event, from any conversation, had every card on screen read its task again, and each read cancelled the one before. With five conversations working at once the events came every 100 to 300 ms and a read took longer, so a card left open never got an answer until the events paused: it read Done for up to 12 s after its task needed the person, showed no Stop, and a Stop click waiting for one timed out. The reads also kept the server busy enough that Stop answered in a second or more. Now only the cards of the conversation the event names read again (a task with no conversation that asked still reads on any), a read under way is let finish and is followed by one more, and the lists finish a read under way before reading again.
0 commit comments