Unverified50% confidenceEventExact time
An approval flow went live on July 7, and the user manual was not updated until July 15; for eight days, the process list in the manual was wrong.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/16/2026
First Seen
Valid until: 10/30/2026
Sources
Related Entities
Related Claims
UnverifiedOn October 10 and 11, the script received a 521 directly when requesting the collection list; because that call had no retry mechanism, the entire phase failed without writing data, whereas URL queries had already had retries added since August.61% similarUnverifiedThe ghealth refresh token for test-status projects expires after 7 days, requiring a weekly re-login.57% similarUnverifiedThe error handling issue was fixed in version 152.0.7977.65 on August 25, the code execution engine issue was fixed in version 152.0.7977.82 on September 3, and the image reading issue was also resolved within the 152 version update cycle.54% 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.53% similarUnverifiedOn September 16, an enterprise payment approval system had version tags applied twice on the same day, and neither version had a changelog or a handover note.52% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1045961API
curl https://kongchang.com/api/v1/knowledge/claims/1045961MCP
get_claim(id=1045961)