nit: improve error message when action is not executed

[xingyaoww]

• This change is worth documenting at https://docs.all-hands.dev/
• Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

End-user friendly description of the problem this fixes or functionality that this introduces.

---

Give a summary of what the PR does, explaining any non-trivial design decisions.

Improve error message (for both human and agent) when action is not executed

---

Link of any specific issues this addresses.

---

To run this PR locally, use the following command:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:e2350d1-nikolaik   --name openhands-app-e2350d1   docker.all-hands.dev/all-hands-ai/openhands:e2350d1

[enyst]

I think this happens also when the user pressed STOP button. I'm checking now if I'm not hallucinating 😅

I'm thinking also... this is a bit interesting message because it feels made for remote, but I don't know how suitable it is for local use. 🤔

If running literally on local runtime, probably not quite right?

[enyst]

I can confirm it happens also when the user presses the 'Stop' button 🤔 which makes sense, that action will never complete (or so we assume or hope!), so we give the agent LLM something with tool_id.

[rbren]

Suggested change

ERROR_ACTION_NOT_EXECUTED = 'The action has not been executed. This likely occurred because the runtime system crashed due to resource limitations. Note that the OpenHands agent has limited resources available for running commands. The agent can retry this action - the runtime system can be rebooted when retrying. However, be aware that any dependencies, environment variables, or other system state previously set up by the agent might be lost after the reboot process.'

ERROR_ACTION_NOT_EXECUTED = 'The action has not been executed. This likely occurred because the runtime system crashed and was rebooted due to resource limitations. Be aware that any dependencies, environment variables, or other system state previously set up by the agent may have been lost after the reboot process.'

Reboot happens on crash, not on next action.

Keeping this reasonably short is probably a good idea too