jackwener/OpenCLI · error · CommandExecutionError

Publish button clicked but result was unclear. Check Weibo m

Error message

Publish button clicked but result was unclear. Check Weibo manually.

What it means

Thrown when the publish button was clicked but the CLI could not determine the outcome: the final-result poll (checking Weibo's success toast / feed for the new post) returned null every iteration until its timeout. The post may actually have succeeded; the automation just cannot confirm it.

Source

Thrown at clis/weibo/publish.js:288

                        for (const m of successMarkers) {
                            if (txt.includes(m) && (txt.includes('成功') || txt.includes('微博'))) {
                                return { ok: true, message: txt };
                            }
                        }
                        for (const m of errorMarkers) {
                            if (txt.includes(m)) {
                                return { ok: false, message: txt };
                            }
                        }
                    }
                    return null;
                })()
            `);
            if (finalResult !== null) break;
        }

        if (!finalResult) {
            throw new CommandExecutionError('Publish button clicked but result was unclear. Check Weibo manually.');
        }

        if (!finalResult.ok) {
            throw new CommandExecutionError(finalResult.message || 'Weibo publish failed');
        }

        return [{
            status: 'success',
            message: finalResult.message || 'Published successfully',
            text,
        }];
    },
});

export const __test__ = {
    validateText,
    validateImagePaths,
};

View on GitHub (pinned to 49907e53dc)

Solutions

Manually check weibo.com — the post often did publish; delete the duplicate if you retry and it went through twice
Retry with fewer/simpler content to reduce post-submit latency
Update the CLI if Weibo changed the success-indicator markup
Slow down: run when network is stable so the result appears within the poll window

Defensive patterns

Strategy: try-catch

Try / catch

try {
    await publishToWeibo(text);
} catch (err) {
    if (String(err.message).includes('result was unclear')) {
        console.warn('Publish result unverified — check weibo.com manually before retrying to avoid duplicates.');
    } else throw err;
}

Prevention

Treat this as 'unknown', not 'failed' — verify on weibo.com before retrying to prevent double-posting
Run with a stable, fast network so the success indicator appears within the poll window
Keep the CLI updated for changed success-toast/feed selectors
Dismiss unexpected popups in the browser profile before automation runs

When it happens

Trigger: After clicking send, the result-polling evaluate never returns a non-null finalResult within the poll budget (page.evaluate returns null on timeout/no match), so `if (!finalResult)` fires.

Common situations: Weibo showed an unexpected dialog after submit (verification, ad popup) that hides the success indicator; the new post took longer than the poll window to appear in the feed; Weibo A/B UI changes moved the success toast/feed item the poll looks for; very slow network delaying feed refresh.

Related errors

AI-assisted analysis of jackwener/OpenCLI@49907e53dc (2026-08-29). Data as JSON: /api/errors/416b7b754fb78699. Report an issue: GitHub.