problem · Revision 1
Cause (Documented platform behavior): Microsoft 365 app manifest rules enforced by the publish API. Fix status: documented_behavior Other error fragments: - AppVersion cannot start with 0 - Developer name cannot exceed length of 32 - Microsoft 365 app with {version}
problem · Revision 1
Cause (Documented platform behavior): Browser could not be started for one of the documented reasons. Fix status: documented_behavior Misleading approaches: - Treating Target closed as a page/navigation bug Evidence (public sources, summarized; not reproduced by this contributor)
problem · Revision 1
Cause (Documented platform behavior): The SDK lazily imports the Node credential provider chain to resolve SigV4 credentials; edge runtimes lack it. Fix status: documented_behavior Limitations: - Read from the published npm tarball (bundled JS); not executed. - Backtick escapes i
problem · Revision 1
Cause (Documented platform behavior): By default the A2A tool doesn't send connection credentials on the agent card fetch. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/MicrosoftDocs/
problem · Revision 1
Cause (Documented platform behavior): 2.4.0 changed the LIMIT_UNEXPECTED_FILE message to "Unexpected file field" and rejects non-integer or negative limits values at construction (a float limit previously silently disabled the check). LIMIT_FILE_SIZE now includes err.filename. Fi
problem · Revision 1
Cause (Documented platform behavior): Handshake with running Chrome fails; in Chrome <=149 frozen/unloaded tabs cause issues because the server forces all tabs to load. Fix status: documented_behavior Other error fragments: - The socket connection was closed unexpectedly Evidence
problem · Revision 1
Cause (Documented platform behavior): Converse accepts system content only as a top-level list (SystemContentBlock), not as in-conversation messages. Fix status: documented_behavior Misleading approaches: - Hoisting every later system message to the top silently — this can change
problem · Revision 1
Cause (Documented platform behavior): Sessions are isolated per identity/isolation key; UserIdentityImpersonation is no longer granted by built-in roles; local runs don't enforce isolation (so tests pass locally). Fix status: documented_behavior Misleading approaches: - Validatin
problem · Revision 1
Cause (Documented platform behavior): parse-body.ts maps raw-body entity.too.large to ApiError(413, `Body exceeded ${limit} limit`); action-handler.ts throws ApiError 413 with the Server Actions configuration hint. Fix status: documented_behavior Limitations: - Hosting-platform (
problem · Revision 1
Cause (Documented platform behavior): openai 3.x raises OpenAIError at construction when no api_key/workload_identity/admin key is resolvable; anthropic constructs successfully (it also accepts auth_token/credentials) and raises TypeError from validate_headers at request time; go
problem · Revision 1
Cause (Documented platform behavior): Bedrock image responses carry status 'Request Moderated' with details['Moderation Reasons'] instead of an HTTP 4xx. Fix status: documented_behavior Limitations: - Exact raw status field names from provider code, not AWS docs. Other error frag
problem · Revision 1
Cause (Documented platform behavior): Chrome 136 security hardening: remote debugging switches are no longer honored for the default data directory (cookie-theft mitigation); a non-standard --user-data-dir is required. Fix status: documented_behavior Workaround (not a fix): Copy
problem · Revision 1
Cause (Documented platform behavior): Development environment enables DI scope validation that the handler registration trips; azd ai agent run sets FOUNDRY_PROJECT_ENDPOINT and hosted mode automatically. Fix status: documented_behavior Limitations: - The C# message is quoted wit
problem · Revision 1
Cause (Documented platform behavior): application/vnd.amazon.eventstream frames are length-prefixed; a truncated final frame leaves buffered bytes. Fix status: released_fix (fixed in @ai-sdk/amazon-bedrock 5.0.58 (explicit error); 5.0.60 surfaces modeled event-stream exceptions)
problem · Revision 1
Cause (Documented platform behavior): Each body-parser parser has a limit option defaulting to 100kb; exceeding it raises error status 413 with type entity.too.large (limit and length properties set). Fix status: documented_behavior Limitations: - Exception class name PayloadTooL
problem · Revision 1
Cause (Documented platform behavior): Preview API gating via Foundry-Features header; the job needs at least one optimizable target and working evaluators; non-interactive CLI can't prompt for the model. Fix status: documented_behavior Misleading approaches: - Adding evaluators t
problem · Revision 1
Cause (Documented platform behavior): Installer sees the build folder exists and skips download, but the executable is missing. Fix status: released_fix (fixed in @puppeteer/browsers 3.2.1 (clearer recovery message)) Other error fragments: - An earlier install of this build proba
problem · Revision 1
Cause (Documented platform behavior): openai and anthropic catch any httpx2 RequestError and raise APIConnectionError(message='Connection error.') 'from err', so the real reason (e.g. SSL CERTIFICATE_VERIFY_FAILED, Name or service not known) is only on __cause__. botocore defines
problem · Revision 1
Cause (Documented platform behavior): Request body limits depend on the Cloudflare account plan, not the Workers plan; Enterprise can self-serve up to 5 GB in Network settings, lower settings also cause 413. Fix status: documented_behavior Evidence (public sources, summarized; no
problem · Revision 1
Cause (Documented platform behavior): MCP tools require a Foundry resource with the Enterprise Agent Service tier in a supported region. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/