Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: non-persistent Responses routes replay stale item ids [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

OpenAI Responses-compatible routes that do not persist Responses items (store=false, or store stripped because a custom provider declares compat.supportsStore=false) can still replay prior Responses item ids on follow-up/tool-turn requests.

For custom Responses-compatible providers, those prior item ids are not available server-side, so the backend can reject follow-up requests with errors such as:

  • 404 Item with id ... not found
  • Items are not persisted when store is set to false

Root Cause

OpenAI Responses-compatible routes that do not persist Responses items (store=false, or store stripped because a custom provider declares compat.supportsStore=false) can still replay prior Responses item ids on follow-up/tool-turn requests.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Summary

OpenAI Responses-compatible routes that do not persist Responses items (store=false, or store stripped because a custom provider declares compat.supportsStore=false) can still replay prior Responses item ids on follow-up/tool-turn requests.

For custom Responses-compatible providers, those prior item ids are not available server-side, so the backend can reject follow-up requests with errors such as:

  • 404 Item with id ... not found
  • Items are not persisted when store is set to false

Impact

This can turn embedded replies or follow-up/tool-turn conversations into user-visible failures like Something went wrong while processing your request for custom OpenAI-compatible Responses providers.

Expected behavior

When the effective Responses request is non-persistent:

  • do not replay previous Responses item ids;
  • do not send stale reasoning/message/function_call item ids from prior Responses output;
  • keep existing item-id replay behavior for store-enabled/persistent OpenAI Responses routes.

Actual behavior

The replay path may include prior Responses output item ids even when the effective request is non-persistent.

Fix PR

A scoped bugfix PR is already open with regression tests and redacted real-backend proof:

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When the effective Responses request is non-persistent:

  • do not replay previous Responses item ids;
  • do not send stale reasoning/message/function_call item ids from prior Responses output;
  • keep existing item-id replay behavior for store-enabled/persistent OpenAI Responses routes.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING