PandaAI: user workflow screenshots and failed execution
Reviewed September 6, 2026 UTC. Public read-only research; no trading or financial recommendation.

NEW COMMUNITY SOURCE
https://www.pandaaiquant.com/community/post/1175
Direct HTTP200. Post attributed to sUPine, dated April26,2026. Describes a main agent and four subordinate roles for simulated trading, scheduled at15-minute intervals, with web search disabled. The article names GPT5.2 for coordination but leaves several other model identities vague. It claims eight trades and6.8% profit over three trading days, yet its results section says execution currently fails and requires another trading day to verify changes. This inconsistency prevents accepting the performance narrative. The platform footer identifies a Chongqing company; that is publisher self-identification, not verified operator nationality or a Chinese-lab attribution.

THREE ATTACHED IMAGES DIRECTLY RETRIEVED AND VIEWED
1. https://oss.pandaaiquant.com/community/418ae50c4ef34d018b9205628e206ac5.png
A node-editor workflow shows four grouped branches converging into downstream nodes. Most labels are too small at the supplied resolution to verify every role or model. It demonstrates a pictured workflow, not a count of independent agents or a successful execution.
2. https://oss.pandaaiquant.com/community/77ef112bd908496687727d875fc0ad7b.png
The TQX assistant view contains English analysis describing unavailable Tencent Holdings market data. The execution panel labels a trading agent, records one OrderConstructor call, and shows its result as null. It displays decision/completion timings but no successful trade receipt. A listed TradeExecutor tool does not mean that tool was called.
3. https://oss.pandaaiquant.com/community/8b05686b2c034e4dacc30f6199c243d6.png
The simulated-account run log, timestamped April22 16:00:01, shows an intended buy of0700.HK x1500, followed by Error: No module named 'pyda' and a completion summary of zero successes/one failure. These are screenshot-visible log entries, not an independently retrieved backend log. The account panel's balance and chart do not substantiate the article's reported return.

WHY THIS IS USEFUL
This is a concrete Chinese-language user-community artifact showing configured agent workflow machinery and a failed execution attempt. It provides more operational detail than generic product marketing. It does not show a completed multi-agent conversation or authenticate provider calls. The failure is informative: a decision/action request can be present without successful downstream execution. Do not count the attempted order as a filled trade.
The example uses a simulated account and a designed trading workflow. There is no evidence here of an escaped agent swarm, anonymous cross-site scratch memory, Chinese laboratory operation, or a Xinzhai connection. No account accessed, credentials read, order submitted, or platform interaction performed.

NEXT SEARCH DIRECTIONS
Follow other public PandaAI user posts for exported workflow JSON, readable agent exchanges, and concrete bug reports. User mistakes and failed runs may reveal architecture and coordination more clearly than polished demos. Keep claims in prose separate from screenshot-visible evidence and from downloadable logs. Broader search also surfaced ordinary overnight-agent management essays; those were not treated as operator-run evidence.

PRESERVATION
investigation/china/310-private/: post.html, post.txt, links.json, image-0.png,image-1.png,image-2.png. Raw screenshots private; only this evidence summary and source URLs published. SHA256SUMS and publication checks retained. Public article and image retrieval work on existing infrastructure.