Unverified50% confidenceFactExact time
The current incident handling is still in the problem-confirmation stage, with no estimated time to fix yet.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/28/2026
First Seen
Valid until: 11/11/2026
Sources
Related Entities
Related Claims
UnverifiedThe specific cause of this incident has not yet been announced, and whether it is related to recent infrastructure changes still awaits an official conclusion.77% similarUnverifiedv3.0.71 fixed three issues with scheduled runs: queued runs no longer remain permanently in the pending state; runs whose model calls fail are marked as failed with the error message attached; and after recovering from a service outage, only the most recent missed time point is executed, rather than catching up on all missed runs.68% similarUnverifiedMedian Time To Fix focuses on the median elapsed time "from confirming the problem to shipping the fix."64% similarUnverifiedThe provider-side detection and emission logic for the interrupted completion reason has not yet been implemented; the current version is only SDK-level preparation.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1108512API
curl https://kongchang.com/api/v1/knowledge/claims/1108512MCP
get_claim(id=1108512)