problem · Revision 1
Cause (Documented platform behavior): Optimistic concurrency on draft workflow. Fix status: documented_behavior Limitations: - Hash-based cause inferred from error name. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com
problem · Revision 1
Cause (Documented platform behavior): The helpers build a message snapshot starting at message_start; ending the request with no snapshot throws 'request ended without sending any chunks' (TS), finalMessage without an assistant message throws 'stream ended without producing a Mes
problem · Revision 1
Cause (Documented platform behavior): Classification is substring-based on the lowercased error text: e.g. 'exceed context limit', "this model's maximum context length is", "is longer than the model's context length", 'input tokens exceed the configured limit', 'exceeds the avail
problem · Revision 1
Cause (Documented platform behavior): The AgentMiddleware base class default for the missing sync/async variant raises NotImplementedError; LangChain does not bridge between the sync and async hooks. Fix status: documented_behavior Limitations: - Message text assembled from adjac
problem · Revision 1
Cause (Documented platform behavior): Each app mode has a dedicated route. Fix status: documented_behavior Limitations: - Route-to-mode mapping from general Dify API knowledge; only error descriptions verified here. Other error fragments: - Please check if your Completion app mod
problem · Revision 1
Cause (Documented platform behavior): Daemon verifies package signatures by default. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/langgenius/dify-plugin-daemon/c798168e4c77890f8f6052
problem · Revision 1
Cause (Documented platform behavior): The api service calls the daemon inner API at PLUGIN_DAEMON_URL with the shared key; transport failures map to these errors. Fix status: documented_behavior Limitations: - Key-mismatch and DB causes inferred from configuration; not an explici
problem · Revision 1
Cause (Documented platform behavior): IDs within one add/upsert call must be unique; validation raises before writing. Fix status: documented_behavior Other error fragments: - Expected IDs to be unique, found Evidence (public sources, summarized; not reproduced by this contributo
problem · Revision 1
Cause (Documented platform behavior): Restricted pickle deserialization by default to prevent code execution from tampered checkpoints. Fix status: documented_behavior Other error fragments: - 'allowed_checkpoint_types' on your checkpoint storage Evidence (public sources, summari
problem · Revision 1
Cause (Documented platform behavior): httpx raises RuntimeError('Cannot send a request, as the client has been closed.') when the client state is CLOSED; SDKs do not catch RuntimeError in their retry loops, so it propagates as-is. Fix status: documented_behavior Limitations: -
problem · Revision 1
Cause (Documented platform behavior): google-genai defines its own APIError hierarchy (ClientError for 4xx, ServerError for 5xx) with .code/.status/.details and str '{code} {status}. {details}'; it does not subclass google.api_core exceptions, whose ResourceExhausted subclasses T
problem · Revision 1
Cause (Documented platform behavior): validate_metadata accepts None but rejects empty dicts. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/chroma-core/chroma/e122af79fd42216d6319ff24
problem · Revision 1
Cause (Documented platform behavior): asyncio Tasks refuse to await a Future belonging to another loop ('Task ... got Future ... attached to a different loop') and asyncio synchronization primitives raise 'is bound to a different event loop' when used from
problem · Revision 1
Cause (Documented platform behavior): Retry only retries methods in allowed_methods (default HEAD, GET, PUT, DELETE, OPTIONS, TRACE); status_forcelist applies only if the method is allowed. RETRY_AFTER_STATUS_CODES (413, 429, 503) honor Retry-After when respect_retry_after_header
problem · Revision 1
Cause (Documented platform behavior): Breaking change #6413: MCP servers are treated as untrusted, so server-initiated sampling is denied unless an approval callback approves it, with default caps _DEFAULT_SAMPLING_MAX_TOKENS=4096 and _DEFAULT_SAMPLING_MAX_REQUESTS=25. In 1.19.0
problem · Revision 1
Cause (Documented platform behavior): Documented error mapping for missing provider credentials. Fix status: documented_behavior Limitations: - List of triggers partly inferred. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercon
problem · Revision 1
Cause (Documented platform behavior): Assertions on connected model inputs. Fix status: documented_behavior Other error fragments: - Please connect a model to the Fallback Model input or disable the fallback option Evidence (public sources, summarized; not reproduced by this cont
problem · Revision 1
Cause (Documented platform behavior): Iteration counter compared against maxIterations option. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/n8n-io/n8n/2f2bac4645472e5efc72c4efedaadff
problem · Revision 1
Cause (Documented platform behavior): Chroma metadata is flat scalar (or homogeneous list) values only; validation rejects other types. Fix status: documented_behavior Other error fragments: - Try filtering complex metadata using langchain_community.vectorstores.utils.filter_comp
problem · Revision 1
Cause (Documented platform behavior): required_variables default changed from None (all optional) to '*' (all required) to avoid silent empty-prompt bugs. Fix status: documented_behavior Other error fragments: - Missing required input variables in ChatPromptBuilder: Evidence (pub