invalid request after failure

[michaelneale]

sometimes after a failure, goose will be unable to continue in its current session:

{"error":"Received error from openai","external_model_message":{"error":{"message":"An assistant message with 'tool_calls' must be followed by tool messages responding to each 'tool_call_id'. The following tool_call_ids did not have response
messages: call_ZJrQE9m4oqSXs1KwqTYI5urC","type":"invalid_request_error","param":"messages.[27].role","code":null}}}

The session will need to be wound back a bit to known good state.

This typically happens after long sessions, when there are timeouts/failures elsewhere.

@lukealvoeiro @baxen I think we need to find a more categorical fix for this as criteria for more wide adoption

[michaelneale]

FYI @lukealvoeiro is working on it as part of checkpoint fixing

[michaelneale]

this looks nicely resolved now