Core update leaves the Discord plugin on an incompatible SDK version

Troubleshooting
, , , ,
1

Adapted community discussion: Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.

Another update left my setup unhealthy. The package changed, the post-update migration failed, and Discord can generate a reply but cannot deliver it. I have a large state directory and want a safe recovery order.

2

Preserve legacy approvals and config before touching the migration. Recover the core Gateway first, then review plugin compatibility one plugin at a time. Do not bulk-update every plugin or delete the approvals file because those actions can hide the original failure and discard policy state.

3

The backup command appeared to run for twenty minutes. The OpenClaw directory is about 66 GB and there is only slightly more free space than that on the same disk.

4

Do not start a second backup. Check whether a backup process still exists, whether the destination is growing, and whether the original terminal printed a verified archive path. With a 66 GB source and limited free space, use another filesystem if the backup failed for capacity. A missing process and no success line means the backup is unverified.

5

The service journal shows the Gateway can process agent turns. Discord is the part failing, and its installed plugin is from an older core release. A missing SDK method appears when the plugin loads.

6

That is a plugin and core version mismatch, not a prompt or channel-token failure. First set the intended system agent so ambient operations have an owner. Then refresh the plugin registry and dry-run an update of Discord only:

openclaw plugins update discord --dry-run

Review any capability changes, apply the targeted update, wait for [gateway] ready, and verify with openclaw channels status --probe. Leave unrelated plugins unchanged until they show their own runtime error.

7

Discord still reports that a reply was generated but could not be delivered. I will apply the targeted Discord plugin update rather than changing every plugin.