Gemini URL retrieval currently sends temperature: 0.1. A development run with a minimal prompt returned HTTP 200 with finishReason: TOO_MANY_TOOL_CALLS and content: {}. Other requests timed out during prefill. Google recommends its default temperature of 1.0 for Gemini 3 because lower settings may cause looping; causation for these failures is not yet confirmed.
The SDK parses content: {} as a truthy content object with parts=None. The client then tries to iterate the absent parts, masking the provider's finish reason with an unexpected error.
Scope:
- Remove the packaged Gemini temperature override, preserving explicit configuration overrides.
- Treat missing or empty content as failed generation and retain its finish reason/message, even if URL retrieval succeeded.
- Add focused offline regressions and update the configuration documentation.
No recipe API, retry, timeout, or concurrency changes. After merge and package promotion to the development recipe Lambda, repeat the same URL and prompt to test the temperature hypothesis. Eric will handle the Lambda dev deployment.
Gemini URL retrieval currently sends
temperature: 0.1. A development run with a minimal prompt returned HTTP 200 withfinishReason: TOO_MANY_TOOL_CALLSandcontent: {}. Other requests timed out during prefill. Google recommends its default temperature of 1.0 for Gemini 3 because lower settings may cause looping; causation for these failures is not yet confirmed.The SDK parses
content: {}as a truthy content object withparts=None. The client then tries to iterate the absent parts, masking the provider's finish reason with an unexpected error.Scope:
No recipe API, retry, timeout, or concurrency changes. After merge and package promotion to the development recipe Lambda, repeat the same URL and prompt to test the temperature hypothesis. Eric will handle the Lambda dev deployment.