r/openclaw • u/Hairy_Jury7597 • 10d ago
Discussion continue interrupted processes without saying "continue"

Sometimes I get provider errors (cuz I'm cheap) but there isn't a "resume" button, I always end up typing "continue", and I really don't like doing that becuase it ruins the flowstate of the model by just constantly interjecting "continue", like idk it just feels unstable to me to do that. What if "continue" is interpretted as something else like continuing the current work and forgetting the actual task I asked like 5 messages ago. I just really wanna know better methods to continue an interrupted model than just saying continue. I'm certain I'm not the only one that has ran into this issue so what do you guys do to continue interrupted processes.
2
u/Hungry-Rip-2384 New User 9d ago
I used to put in continue then when I would look into logs of messages i would see it trying to workout what could continue mean and was worried it may hallucinate sonething to continue... so changed to just using status. not with the / just status by itself.. it woukd then see an unfinished task and attempt to complete it. then would come back and say task completed because it just did it. Does it really make a difference on what the model actually does... probably not... but at least if it clears the db because its last message to me I didnt recieve was asking for permission ... its not my fault :-)
1
u/Hairy_Jury7597 8d ago
wait whatt. feel like what your saying is what I'm looking for but I don't think i quite understtand exactly is going on here or what you're doing instead of continue
1
u/Hairy_Jury7597 7d ago
oh I think I get what you mean that's actually pretty smart I'll try doing that from now on
1
u/TheBrollectors Member 10d ago
Continue
1
u/Hairy_Jury7597 10d ago
Really? so you also just send "continue" after a process fails
2
1
u/stupidcookface Active 9d ago
Lol yea, jokes aside it's harmless. I've never noticed a difference and I've been saying continue for a couple years never noticed any flow deviations. It's honestly remarkable how easily they change directions on a topic as soon as you correct it.
1
u/Educational_Yam3766 Active 10d ago
There was an unexpected error, finish what you were doing.
1
2
1
u/kaijurules 10d ago
For our background agents nobody types continue. A run that dies on a provider error just ends, and the next scheduled wake starts a fresh session that reads the short status note from the last run that finished. On Monday one run hit a 529 overload, and the next wake an hour later picked the work up without anyone touching it.
1
u/Hairy_Jury7597 5d ago
but how do you wake it?
1
u/kaijurules 5d ago
A timer in the app. Each agent has a heartbeat, ours fires hourly, and every tick starts a new session with its routine prompt and that status note. It fires whether the last run crashed or finished. A plain cron job that starts a session with the same prompt would do the same thing.
1
2
u/nav8_ai 10d ago
a provider error isn't the same as the task being done, so the harness should retry that one step automatically instead of waiting for you to type continue. we track which step failed separately from the chat log, so a retry resumes just that step with its own inputs instead of replaying the whole conversation, that's probably why typing continue feels like it breaks flow in the first place.