INWORLD REQUEST-ID WORKSHEET Resource checked October 17, 2026 Companion: https://burki.dev/blog/inworld-request-ids-voice-api-troubleshooting This free worksheet is an original planning resource. No requests, calls or support messages were sent for it. Provider usage is separate. Blank fields are unknown, not successful results. Use only evidence you are authorized to access. 1. DEFINE THE PROBLEM Environment/workspace reference: _____________________________________________ Observed issue in one sentence: ______________________________________________ UTC incident window: ________________________________________________________ Expected application behavior: _______________________________________________ What was actually observed: __________________________________________________ What remains unknown: ________________________________________________________ 2. KEEP THE IDENTIFIERS SEPARATE Internal conversation reference: _____________________________________________ Local turn reference: ________________________________________________________ Local attempt reference: _____________________________________________________ x-inworld-client-request-id value sent, or not captured: ______________________ x-request-id value returned, or not observed: _________________________________ Separate business-operation reference, if applicable: _________________________ These two header names follow Inworld's October 5 announcement. A correlation value is not proof of idempotency, audio delivery or a completed business action. Source: https://inworld.ai/productlog 3. CAPTURE ONE ATTEMPT PER ROW Repeat this block for every separately authorized submission. Attempt reference: __________________________________________________________ UTC submission/response times: ________________________________________________ Transport/endpoint: __________________________________________________________ Requested model and voice: ___________________________________________________ Client/library and application version: ______________________________________ HTTP response/status, or response not observed: ______________________________ Provider identifier captured? _______________________________________________ Audio received: yes / no / unknown Playback observed: yes / no / unknown Caller-heard outcome supported by what evidence? _____________________________ Application result accepted / rejected / stale / unknown: _____________________ Usage evidence reference, or unknown: ________________________________________ Do not paste authentication headers, credentials, signed recording URLs or caller content into this worksheet. Use an internal evidence reference with suitable access restrictions. Keep context or connection IDs under their own names. 4. FICTIONAL TIMEOUT EXERCISE, NOT A RUN RESULT Conversation demo-conversation-01, turn reply-03: A. Client submits opaque-attempt-a; response is not observed before timeout. B. A separately authorized retry uses opaque-attempt-b; a response later arrives. C. Preserve both attempts. Check whether any late A result entered playback. Record your conclusion: A provider outcome: __________________________________________________________ B provider outcome: __________________________________________________________ Actual application playback: __________________________________________________ Business action involved? If so, review separately: ___________________________ Reason a future retry would be allowed or withheld: ___________________________ Never fill A's missing provider ID with B's ID. A timeout alone does not resolve whether the original attempt reached the provider or incurred usage. 5. PREPARE A MINIMAL SUPPORT RECORD FOR REVIEW Problem summary: ____________________________________________________________ UTC window and environment: __________________________________________________ Endpoint/model/client version: _______________________________________________ Client correlation value and returned server ID, separately labeled: __________ Observed error and minimal synthetic reproduction description: _______________ Internal evidence reference: __________________________________________________ What assistance is requested? ________________________________________________ Private content excluded or explicitly authorized: ___________________________ Prepared by / reviewed by / date: _____________________________________________ Submission status: not sent / separately authorized and sent / unknown Support outcome, with evidence: ______________________________________________ Contact reference only: https://docs.inworld.ai/portal/support This template does not submit a support ticket or promise resolution. 6. BURKI EVIDENCE AND COST CHECK Open Calls and locate the relevant record in Call history if authorized. Keep its application ID distinct from a provider request ID. Native Inworld TTS header capture is not verified by this guide; do not invent a missing dashboard value. Available application evidence reference: ____________________________________ Provider capture present / absent / unknown: __________________________________ Scope of any proposed new test and its authorization: _________________________ Account/model price checked on: ______________________________________________ Assumed billable quantity and unit: ___________________________________________ Actual invoice/usage reference, if available: __________________________________ Other platform/provider/carrier charges: ______________________________________ Review outcome: evidence sufficient / capture gap / more review required Next owner and concrete next step: ____________________________________________