Field SOP
Field SOP

Yuanqi Is Down: Why Your Legacy Workflow Can't Be Exported?

Tencent Yuanqi formally shut down on November 9, 2026: application access, data read/write, API calls and the console are all closed, and agents published to Official Accounts, service accounts or WeChat Customer Service no longer respond. Every figure in this checklist comes from four official pages (discontinuation notice, data-export guide, ADP migration guide, refund guide), arranged as a five-step salvage plan: new-agent creation and API key issuance stopped October 29; before shutdown, self-service export paths cover conversation records, knowledge bases, workflows and Widgets with per-space one-click export; after shutdown and until January 9, 2027 the data-export console still delivers backups, after which all user data is deleted; migration targets the officially named Tencent Cloud Agent Development Platform (ADP), where knowledge bases, new-version workflows and Widgets import directly, but the official guide states verbatim that legacy Yuanqi workflows cannot be exported and must be rebuilt by hand, plugins must be recreated as custom tools, and the two platforms' official models and plugins differ enough that answers may change; refunds cover only unconsumed Hunyuan prepaid resource packs bought on Tencent Cloud for legacy API calls, with post-paid billing closed first as officially warned to affect other post-paid services, and 5-10 business days for a refund after review.

Published November 10, 20269 min read
<!-- yuanqi-shutdown-migration-sop | sop | Yuanqi Is Down: Why Your Legacy Workflow Can't Be Exported? -->

If one of the agents you built on Tencent Yuanqi is wired into your WeChat Official Account, it has already gone silent. As of November 9, 2026, Yuanqi has formally shut down. The official discontinuation notice states it plainly: the platform has closed application access, data read/write, API calls, and console usage — every public-facing service — and agents published through Yuanqi to channels such as Official Accounts, service accounts, and WeChat Customer Service no longer respond to user conversations. The cut lands in a painful spot: your agent never ran on your own servers. It lived on the platform, and once the platform closes, you cannot even get in to look around.

First, the division of labor among this batch's four pieces. The Qoduck hotspot piece dissects the official framing around a newly launched anonymous model; the Kinference deep dive examines an inference routing control plane that decides where cluster-side requests should go; the five-provider free hosted API comparison lines up what each free tier gives, restricts, and takes in exchange for data. This column covers none of that. It serves one audience only — existing Yuanqi users — and hands them a damage-control playbook executed against a fixed timeline. It also differs from the Tencent Buddy One product report: that piece asks what a new product looks like; this one asks which button you should press next now that an old platform has closed.

As of November 9, 2026, every claim in this article comes from four official Yuanqi pages: the discontinuation notice, the user data export guide, the Yuanqi-to-ADP migration guide, and the refund guide for legacy Yuanqi external services, all under yuanqi.tencent.com/cl/. Where the official pages give no detail, this article invents none; where they attach a warning, this article repeats every one.

1. Map the Timeline First: Which Window Are You In

The official discontinuation notice splits the wind-down into four segments. The first thing to do is not to start clicking around, but to figure out which segment you are standing in:

  • From October 29, 2026: creation of new agents and distribution of new API keys stopped. If your agent had been running normally, you likely felt nothing that day — but it was the starting gun for the countdown.
  • November 9, 2026: formal shutdown. Application access, data read/write, API calls, and console usage all closed; agents published to Official Accounts, service accounts, WeChat Customer Service, and other channels stopped responding. Channel-side silence and platform-side lockout happened on the same day — no grace period.
  • November 9, 2026 to January 9, 2027: platform features are disabled, but you can still log in to the Yuanqi data export console, submit an export request, and download backup data — the only door left open.
  • From January 9, 2027: except for logs and records that laws and regulations require to be retained, all user data will be deleted.

Pin those four lines somewhere visible. The export window is roughly two months, and after January 9, 2027 no remedy exists — not "inconvenient," but "physically gone." Every step below rests on one premise: move early, and do not gamble on deadline week.

2. Pre-Shutdown Self-Service Export: Audit What You Grabbed

If you self-exported through the console before shutdown, audit your coverage against the official data export guide: did you take everything you will need? If you never exported, or only exported part of it, the export console in the next section still lets you catch up. The guide lists four paths, reproduced here as written:

  • Conversation records: select the agent > App Operations > Conversation Records > Export
  • Knowledge base: Knowledge Base > select a knowledge base > Documents/Q&A > Download
  • Workflow: select the agent > Workflow Management > More > Export
  • Widget: Widget Plaza > Widget Development > select a Widget > Export

If clicking through item by item sounds tedious, there is a space-level bulk route: select the space you want to export, choose "one-click export of all data," then download the archive. This suits accounts holding a pile of agents you have not logged into for months — grab the whole bundle first, sort it out later.

The official export scope covers six categories: agent configuration, knowledge bases, custom plugins, conversation records, workflows, and Widgets. One qualifier hides in that list, and it matters: the official pages note "conversation records (new-version Yuanqi only)." That single line decides what to expect next. If your account runs on legacy Yuanqi, conversation records are simply not among the data you can take out through official channels. Accept that constraint first, then plan around it.

3. After Shutdown: The Data Export Console Is the Only Door

After shutdown, the original application entry and console are closed. The opening left behind is the Yuanqi data export console: between November 9, 2026 and January 9, 2027, you can log in with your account credentials, submit an export request, and download backup data. Three reminders:

  1. Export by space. The flow is the same three steps: select the space, one-click export of all data, download the archive. Before you start, inventory your account: which spaces exist, how many agents hang in each, which ones were "in production" on an Official Account or WeChat Customer Service. Do not export only the live ones — old agents often hold months of accumulated prompts and knowledge bases.
  2. Do not push the export to the end of the window. The official pages state data will be deleted starting January 9, 2027, and that date will not move because of your network problems or account issues. Exporting costs almost nothing; the payoff is the entire dataset.
  3. A successful export is not a completed migration. Backup files on a local disk do not make your Official Account agent speak again. The actual recovery is the next step.

4. Migrating to ADP: Import What You Can, Rebuild What You Can't

The officially named successor is Tencent Cloud's Agent Development Platform (ADP), with its own migration guide page. How much work this step takes depends almost entirely on whether your account runs the new version or the legacy version of Yuanqi — the single most important distinction in this article, because the two versions take completely different paths here.

What imports directly into ADP, three items: knowledge bases, workflows (new version), and Widgets. Use the "batch import" capability on the ADP side. If your agents were all built on new-version Yuanqi, the bulk of the migration just got much cheaper.

What must be rebuilt manually, three categories:

  1. Legacy Yuanqi workflows. This is the heaviest sentence in the official migration guide: workflows on legacy Yuanqi do not currently support export, and users need to rebuild them manually in ADP, referring to the nodes and logic of the original workflow. There is no batch channel and no format conversion tool; the only officially given method is manual rebuilding. In practice: first document the original workflow's nodes, connections, and per-node configuration (the workflow file exported before shutdown earns its keep here); then rebuild node by node in ADP against that documentation. Rebuilding from memory is the easiest way to lose a branch.
  2. Agent settings. Model settings, prompts, tool invocations, welcome messages, and sample questions must be migrated item by item; the application mode should match the original agent among standard, Multi-Agent, or single-workflow. For prompts, copy the whole text rather than rewriting from impression — prompts are exactly where "feels about the same, performs very differently" happens.
  3. Plugins. Yuanqi's plugin plaza corresponds to "custom tools" in ADP, and each one must be manually recreated there. Three plugins in Yuanqi means three custom tools to rebuild in ADP.

On the same page, the officials attached a warning to take seriously: the official models and official plugins provided by the two platforms are not identical, and conversation quality may differ after migration. Translated into operating instructions: finishing the migration is not the finish line. Run your original test questions against the new platform and compare responses; if quality drops, adjust model settings and prompts.

Channel coverage needs a check too. ADP covers subscription accounts, service accounts, WeChat Customer Service, WeChat Mini Programs, WeCom, DingTalk, Feishu, and more; but QQ Browser, YingYongBao, and Honor — channels Yuanqi supported — are not in ADP's channel mapping table. For agents published to those three channels, the official pages offer no corresponding successor path. The official announcement recommends no third-party platform, and this article likewise recommends none.

The officials named exactly two alternatives: the Tencent Cloud Agent Development Platform (ADP), and the built-in intelligent reply feature of Official Accounts. If your agent was nothing more than simple Q&A inside an Official Account, the built-in reply costs the least; if it depended on knowledge bases, workflows, or plugins, ADP is the matching surface.

5. Refunds and Cleanup: Only One Kind of Resource Package Qualifies

If you purchased Hunyuan prepaid resource packages through Tencent Cloud and used them for legacy Yuanqi API calls, the official refund guide draws a narrow line. Check yourself against it before submitting anything:

  • Refundable: Hunyuan prepaid resource packages purchased through Tencent Cloud, used for legacy Yuanqi API calls, with unused balance remaining.
  • Not refundable: free complimentary packages, already-consumed portions, and expired packages.

The process contains one easily tripped step, which the officials specifically flagged: close pay-as-you-go billing first, then check the resource package balance and submit a ticket through after-sales support. Closing pay-as-you-go billing, per the official reminder, affects other businesses under the same Tencent Cloud account that depend on it. If other services run on that account, assess the blast radius before touching anything — do not sever a second business to reclaim one package. After the ticket passes review, funds return via the original payment path within 5 to 10 business days.

A final cleanup checklist. One: data backed up from the Yuanqi data export console. Two: agent configuration, knowledge bases, and workflows live on ADP (or switched to the Official Account intelligent reply). Three: plugins and agent settings recreated and validated against your original test questions. Four: pay-as-you-go billing evaluated against the official warning, and the refund ticket submitted. Do these four things, and your total loss narrows to the labor hours spent rebuilding legacy workflows — precisely the one step for which the officials offered no shortcut.

FAQ

Q1: Can I still log in to the Yuanqi platform after shutdown? A1: No. The official discontinuation notice states that from November 9, 2026, application access, data read/write, API calls, and console usage — all public-facing services — are closed. The only exception is the Yuanqi data export console: between November 9, 2026 and January 9, 2027, you can still log in, submit an export request, and download backup data.

Q2: My workflow cannot be exported. What now? A2: First confirm whether you are on new-version or legacy Yuanqi — the two have completely different rules. The official migration guide to ADP states that workflows on legacy Yuanqi do not currently support export and must be rebuilt manually in ADP, referring to the nodes and logic of the original workflow. New-version workflows can be exported and batch-imported into ADP. For legacy workflows there is no shortcut, only manual rebuilding against the original nodes and logic.

Q3: Do agents published to Official Accounts and WeChat Customer Service still work? A3: No. The official notice states that agents published through Yuanqi to Official Accounts, service accounts, WeChat Customer Service, and other channels no longer respond to user conversations after shutdown. To restore automated replies on the Official Account side, the officially named options are the Official Account intelligent reply, or migrating to Tencent Cloud's Agent Development Platform (ADP) and reconnecting the corresponding channel. ADP's channel mapping covers subscription accounts, service accounts, WeChat Customer Service, WeChat Mini Programs, WeCom, DingTalk, Feishu, and more — but QQ Browser, YingYongBao, and Honor are not in the table.

Q4: Are all the Hunyuan resource packages I bought refundable? A4: No. Per the official refund guide, only Hunyuan prepaid resource packages purchased through Tencent Cloud, used for legacy Yuanqi API calls, with unused balance remaining are refundable. Free complimentary packages, consumed portions, and expired packages are all excluded. The process: close pay-as-you-go billing first — the official reminder says this affects other businesses under the same Tencent Cloud account that depend on pay-as-you-go billing — then check the package balance and submit a ticket through after-sales support. After review, funds return via the original payment path within 5 to 10 business days.

Q5: What is the last possible date to export my data? A5: Before January 9, 2027. The official pages state that from January 9, 2027 onward, except for logs and records that laws and regulations require to be retained, all user data will be deleted. Export requests must be submitted through the Yuanqi data export console within the window from November 9, 2026 to January 9, 2027. The window lasts roughly two months; move early rather than gambling on the deadline.

Related reading

This article is AI-assisted and human-edited. Last updated: 2026-11-10

FAQ

Can I still log in to the Yuanqi platform after shutdown?
No. The official discontinuation notice states that from November 9, 2026, application access, data read/write, API calls, and console usage — all public-facing services — are closed. The only exception is the Yuanqi data export console: between November 9, 2026 and January 9, 2027, you can still log in, submit an export request, and download backup data.
My workflow cannot be exported. What now?
First confirm whether you are on new-version or legacy Yuanqi — the two have completely different rules. The official migration guide to ADP states that workflows on legacy Yuanqi do not currently support export and must be rebuilt manually in ADP, referring to the nodes and logic of the original workflow. New-version workflows can be exported and batch-imported into ADP. For legacy workflows there is no shortcut, only manual rebuilding against the original nodes and logic.
Do agents published to Official Accounts and WeChat Customer Service still work?
No. The official notice states that agents published through Yuanqi to Official Accounts, service accounts, WeChat Customer Service, and other channels no longer respond to user conversations after shutdown. To restore automated replies on the Official Account side, the officially named options are the Official Account intelligent reply, or migrating to Tencent Cloud's Agent Development Platform (ADP) and reconnecting the corresponding channel. ADP's channel mapping covers subscription accounts, service accounts, WeChat Customer Service, WeChat Mini Programs, WeCom, DingTalk, Feishu, and more — but QQ Browser, YingYongBao, and Honor are not in the table.
Are all the Hunyuan resource packages I bought refundable?
No. Per the official refund guide, only Hunyuan prepaid resource packages purchased through Tencent Cloud, used for legacy Yuanqi API calls, with unused balance remaining are refundable. Free complimentary packages, consumed portions, and expired packages are all excluded. The process: close pay-as-you-go billing first — the official reminder says this affects other businesses under the same Tencent Cloud account that depend on pay-as-you-go billing — then check the package balance and submit a ticket through after-sales support. After review, funds return via the original payment path within 5 to 10 business days.
What is the last possible date to export my data?
Before January 9, 2027. The official pages state that from January 9, 2027 onward, except for logs and records that laws and regulations require to be retained, all user data will be deleted. Export requests must be submitted through the Yuanqi data export console within the window from November 9, 2026 to January 9, 2027. The window lasts roughly two months; move early rather than gambling on the deadline.

Related

Field SOP

GitHub Copilot: Six Models Deprecated December 14, What to Fix

Six GitHub Copilot models are deprecated on December 14, 2026, and the official November 13, 2026 changelog gives six migration sentences but no configuration file name, model ID string or migration script. This SOP turns those sentences into a checkable list: replace hardcoded model names in workflows and integrations, enable model policies in Copilot settings, and understand what global default, the model selector, Copilot Chat, inline edits and code completions each do. All six model names and suggested alternatives are quoted as published, Kimi K3 stays To be announced, and the Claude Haiku 4.5 annual-plan exception for individual subscribers is spelled out.

Nov 16, 20269 min read
Field SOP

Bedrock AgentCore V2 Snapshots: Four Patterns, One Pre-warm

Turns the four official AWS section names into a checkable sequence for Bedrock AgentCore runtime V2 session startup: measure Latency and OverheadLatency in CloudWatch first, move imports and static data into init, use Working with hooks for build-time large files, then send a background warm-up request with Pre-warm on user engagement and keep the session ID. It records the 120-second /ping gate, that the V2 default applies only to new and updated runtimes, that existing ones need explicit platformVersion=V2, and that the sample code is for non-production use. The Region and cold-start discrepancies between the two official pages are kept side by side.

Nov 15, 20269 min read