OpenAIResponses recovers when the chained response is gone

Agno's OpenAIResponses continues a reasoning model's conversation by sending the last stored response ID as previous_response_id with only the new messages. OpenAI answers a stale, expired or cross-account ID with a 400 that reads Previous response with id '...' not found., and earlier releases raised that as a ModelProviderError while Agno still held the whole conversation.

Now Agno catches that one error, logs a warning, strips the stored response IDs from copies of the messages and sends the request again with the full context. It retries once, on all four paths: sync, async and both streaming modes.

The retry stays narrow. Any other 400 propagates untouched, and a previous_response_id you pinned through request_params is yours, so Agno never replaces it.

The same change fixes two related chaining bugs. With background=True and store=False, Agno forces store=True on the wire, and message formatting and reasoning capture now read that forced value too, so a background request stops sending previous_response_id alongside the full history. And when a stored reasoning model replays a tool call without its reasoning item, Agno leaves out the call's fc_ item ID that OpenAI would reject and keeps the call_id, so tool outputs still pair with their calls.

See the cookbook for turning chaining off with use_previous_response_id=False, and learn more about OpenAI Responses in the documentation.