problem · Revision 1
Cause (Documented platform behavior): SDKs refuse to mix a partial static credential with the default chain. Fix status: documented_behavior Limitations: - Read from the published npm tarball (bundled JS); not executed. Other error fragments: - Both must be provided together,
problem · Revision 1
Cause (Documented platform behavior): detectBrowserPlatform maps linux+arm64 to LINUX_ARM, but the CfT folder is 'linux-arm64' only for buildId >= 153.0.8001.0 (earlier builds map to 'linux64'); platforms outside darwin/linux/win32 return undefined and the installer throws. Fix s
problem · Revision 1
Cause (Documented platform behavior): The ML CLI and SDK target the MachineLearningServices provider, which doesn't support new Foundry projects. Fix status: documented_behavior Limitations: - exact string is generic; match together with product/context Evidence (public sources,
problem · Revision 1
Cause (Documented platform behavior): Cloudflare returns 524 when the origin does not respond before the Proxy Read Timeout (default 125 s); only Enterprise zones can raise it (up to 6,000 s). A 30 s Proxy Write Timeout also produces 524
problem · Revision 1
Cause (Documented platform behavior): Each SDK wraps (or does not wrap) its transport's timeout differently. openai/anthropic catch httpx2 TimeoutException and raise APITimeoutError (a subclass of APIConnectionError) after retries; defaults are 600 s total / 5 s connect. botocore
problem · Revision 1
Cause (Documented platform behavior): Nova 2 uses its own reasoningConfig {type:'enabled', maxReasoningEffort} in additionalModelRequestFields. Fix status: documented_behavior Limitations: - Validation shown is client-side (langchain-aws, LiteLLM); server error text not captured.
problem · Revision 1
Cause (Documented platform behavior): Key-based authentication isn't supported with private virtual networking for the AI Search tool. Fix status: documented_behavior Misleading approaches: - Debugging DNS/private endpoints first; the documented cause is the auth type. Other erro
problem · Revision 1
Cause (Documented platform behavior): Downloaded file lives on the remote browser host, so path() is unavailable (documented: 'The method throws when connected remotely'); the remote browser's localhost is not the client's localhost unless exposeNetwork forwards it. Fix status: d
problem · Revision 1
Cause (Documented platform behavior): Converse RequestMetadata map is constrained (max 16; key/value patterns) for invocation-log filtering. Fix status: documented_behavior Limitations: - LiteLLM validates client-side; the raw Bedrock error text for violations is not captured her
problem · Revision 1
Cause (Documented platform behavior): proxy_read_timeout is measured between two successive read operations, not for the whole response; if the proxied server sends nothing within it, nginx closes the connection. Fix status: documented_behavior Limitations: - exact string is gene
problem · Revision 1
Cause (Documented platform behavior): The configured custom search instance cannot be found in the connected resource. Fix status: documented_behavior Other error fragments: - Instance or Customer not found - Tool_User_Error Evidence (public sources, summarized; not reproduced by
problem · Revision 1
Cause (Documented platform behavior): With reuseExistingServer false, the plugin throws if the url/port already responds; if the command exits, it reports the exit code. Fix status: documented_behavior Other error fragments: - Process from config.webServer was not able to start.
problem · Revision 1
Cause (Documented platform behavior): OpenSSL's X509_V_ERR_CERT_NOT_YET_VALID/CERT_HAS_EXPIRED verification errors; OpenSSL master reworded the not-yet-valid text to mention an incorrect system clock (3.5.0 still says 'certificate is not yet valid'). Node exposes the same conditi
problem · Revision 1
Cause (Documented platform behavior): nginx rejects bodies above client_max_body_size with 413 and logs "client intended to send too large body: N bytes"; size 0 disables the check. Fix status: documented_behavior Misleading approaches: - Increasing the application framework limi
problem · Revision 1
Cause (Documented platform behavior): Toolbox tools must be uniquely identifiable (server_label); the toolbox MCP server doesn't implement ping or prompts/list and only supports streaming tools/call. Tool names are prefixed '{server_label}.{tool_name}'. Fix status: documented_beh
problem · Revision 1
Cause (Documented platform behavior): Readiness probe never succeeds: with Node 17+ 'localhost' may resolve to ::1 first while the server listens on IPv4 (reported in #20784); or startup legitimately exceeds webServer.timeout (default 60000 ms). Also the url must return 2xx/3xx/4
problem · Revision 1
Cause (Documented platform behavior): Documented: once the response has started the status code is not changed; errors are sent as an object with an error property in the NDJSON stream. Non-stream errors use normal statuses (400/404/429/500, 502 when a cloud
problem · Revision 1
Cause (Documented platform behavior): The libraries hard-code a 5 minute tolerance for replay protection; the timestamp is part of the signed content, so it cannot be edited. Fix status: documented_behavior Other error fragments: - Message timestamp too new - Invalid
problem · Revision 1
Cause (Documented platform behavior): Agent Service refreshes OAuth tokens using the connection's refresh URL and refresh token; if refresh fails the user must consent again. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor)
problem · Revision 1
Cause (Documented platform behavior): Mantle auth mints short-term Bedrock API keys (bearer tokens) from AWS credentials via aws-bedrock-token-generator; endpoints and regions must be explicit. Fix status: documented_behavior Limitations: - Short-term keys are capped at 12h lifet