Recommended action: For agent loops, disable AFC (automatic_function_calling={'disable': True}) and execute tools yourself, or raise maximum_remote_calls and check response.function_calls before reading text. Option: Control tool execution explicitly [evidence: official_recommend
Recommended action: Set models[].requestOptions.caBundlePath to the PEM chain (clientCertificate for mTLS); verify with curl --cacert; verifySsl:false only as a temporary diagnostic. Option: Configure caBundlePath [evidence: official_recommended_action] Applies when: see problem
Recommended action: Attach RBPs to both the guardrail and the guardrail profile (console), create an immutable guardrail version, verify ApplyGuardrail from a member account before enforcing, and configure enforcement per region. Option: Attach RBPs to guardrail and guardrail pro
Recommended action: Export GH_TOKEN from a secret (env: GH_TOKEN: ${{ github.token }} in Actions) rather than running interactive login in automation. Option: Provide GH_TOKEN [evidence: official_recommended_action] Applies when: See trigger Steps: 1. GitHub Actions: env: GH_TOKE
Recommended action: Set HTTPS_PROXY=http://proxy:port (the scheme describes how to talk to the proxy, not the target). Option: Use http:// proxy scheme [evidence: official_recommended_action] Applies when: See trigger Steps: 1. export HTTPS_PROXY=http://proxy.example:3128 (and HT
Recommended action: Use absolute command paths (e.g. /usr/local/bin/npx from `which npx`) in mcpServers config. Option: Use absolute command path [evidence: documented_workaround] Applies when: see problem Steps: 1. which npx 2. mcpServers: command: /usr/local/bin/npx Expected: S
Recommended action: Either fix/replace the environment variable value, or unset it (unset GH_TOKEN GITHUB_TOKEN) before gh auth login; check which source is active with gh auth status. Option: Clear the env token or update it [evidence: official_recommended_action] Applies when:
Recommended action: In the portal Foundry resource page select Manage deleted resources and purge the resource tied to the VNet, or run the template's deleteCaphost.sh script, then delete the subnet. Option: Purge soft-deleted Foundry resource [evidence: official_recommended_acti
Recommended action: Map all enum values explicitly: max_tokens and model_context_window_exceeded → length/truncated; guardrail_intervened and content_filtered → content_filter; malformed_model_output/malformed_tool_use → error with retry; read stopReason on both streaming (messag
Recommended action: Model maps as arrays of {key, value} objects, or disable strict for that tool/output (strict_json_schema=False / non-strict function tool). Option: Replace dicts with key/value arrays or opt out of strict [evidence: documented_workaround] Applies when: See tri
Recommended action: Resync the guest clock (sudo hwclock -s, or ntpdate/chrony/systemd-timesyncd via systemd or a [boot] command in /etc/wsl.conf), or restart the VM with wsl --shutdown; do not disable apt date checks. Option: Resync the WSL clock [evidence: documented_workaround
Recommended action: In automation do not run gh auth login; set GH_TOKEN (or GITHUB_TOKEN in Actions) or pipe a token with --with-token. If a human must authorize, relay the URL/code to them explicitly and keep the process alive. Option: Use
Recommended action: Drop empty/whitespace-only text blocks before sending (keep non-empty ones), especially next to tool_use and reasoning blocks. Option: Filter empty text blocks [evidence: documented_workaround] Steps: 1. Before each request remove text blocks whose text.strip(
Recommended action: If you depend on HTTP/1.1 behavior or see GOAWAY failures, set allowH2: false on the Client/Agent used by your SDK; otherwise retry idempotent requests on GOAWAY SocketErrors. Option: Pin HTTP/1.1 [evidence: official_recommended_action] Applies when: See trigg
Recommended action: Test on windows-2025-vs2026; upgrade node-gyp (>= 12.1, ideally >= 13.0.1) / npm, update CMake generator to 'Visual Studio 18 2026' or let CMake auto-detect; or pin runs-on: windows-2022 while migrating. Option: Upgrade native toolchain detection or pin window
Recommended action: Enable Device Flow in the app settings and pass only client_id (and grant_type urn:ietf:params:oauth:grant-type:device_code when polling). Option: Enable device flow for the app [evidence: official_recommended_action] Applies when: See trigger Steps: 1. App se
Recommended action: Set all three BYO resources on the account/project via capability settings before creating the project; if the project already exists, delete and recreate it with the settings. Option: Provide all three BYO connections [evidence: official_recommended_action] S