Establish what is happening
Label the request environment
Record endpoint origin, selected environment, credential label, client revision, and request time without secrets. Note the expected test or live resource and the marker actually returned. Preserve the configuration source so a shell override is not mistaken for checked-in state.
Compare endpoint and identity
Run a harmless request with matching test configuration and matching production configuration when permitted. Compare URL, credential label, resource identifier, and response marker. A rejected cross-environment lookup narrows the boundary; it does not justify trying another credential.
Bound mixed records
Group cases by endpoint, environment, credential label, resource marker, and client revision. Separate configuration mismatch, copied identifier, missing marker, and remote rejection. Quarantine any record whose environment cannot be established before further reads or writes.
What to carry forward
Triage ends with one labeled request, endpoint and credential comparison, resource marker, and affected cohort. Stop before retrying across environments. Route configuration, identity, and resource questions separately. Keep complete destination evidence protected during a safe review.
Technical background: OpenAI documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow