RESPONSE_LOST — the indeterminate write

A state-changing request whose 2xx status line arrived but whose response body was lost answers RESPONSE_LOST (status 502, exit 10): the server accepted the write and the outcome is unknown. Verify with the matching list/get before writing again — do NOT retry. Exit 1 is the documented retryable exit, and this is deliberately not it: retrying a landed write duplicates it. The verify-then-decide pattern, as a script:

octolens feeds create --name Watchlist --filter-json '{"conditions":[{"field":"Source","values":"reddit"}]}' --json
if [ $? -eq 10 ]; then
  # the write may have landed - VERIFY instead of re-running the create
  octolens feeds list --json | jq -e '.data[] | select(.name == "Watchlist")' >/dev/null &&
    echo "create landed - do not repeat it" >&2
fi

Get started

Contract

Commands

Concepts

Guides

Scripting & agents

RESPONSE_LOST — the indeterminate write