chenhg5/cc-connect · error

reconstruct reply context: %w

Error message

reconstruct reply context: %w

What it means

Cron run path: after optional cron reply-target resolution, replyCtx is still nil, and ReconstructReplyCtx(runSessionKey) failed — the persisted session key could not be rebuilt into a reply target (unknown platform prefix or malformed key). The cron run is aborted so the agent response is never sent.

Source

Thrown at core/engine.go:1529

			resolvedSessionKey, resolvedReplyCtx, err := resolver.ResolveCronReplyTarget(sessionKey, cronRunTitle(job))
			if err != nil {
				if !errors.Is(err, ErrNotSupported) {
					return fmt.Errorf("resolve cron reply target: %w", err)
				}
			} else {
				if resolvedSessionKey != "" {
					runSessionKey = resolvedSessionKey
				}
				if resolvedReplyCtx != nil {
					replyCtx = resolvedReplyCtx
				}
			}
		}
	}
	if replyCtx == nil {
		replyCtx, err = rc.ReconstructReplyCtx(runSessionKey)
		if err != nil {
			return fmt.Errorf("reconstruct reply context: %w", err)
		}
	}

	// Wrap platform to discard all outgoing messages when muted
	effectivePlatform := targetPlatform
	if job.Mute {
		effectivePlatform = &mutePlatform{targetPlatform}
	}

	// Notify user that a cron job is executing (unless silent/muted)
	// Note: this notification uses targetPlatform directly, not the tracking wrapper,
	// so it won't count as a "meaningful delivery" for empty response detection.
	if !job.Mute {
		silent := false
		if e.cronScheduler != nil {
			silent = e.cronScheduler.IsSilent(job)
		}
		if !silent {

View on GitHub (pinned to 4000b2338a)

Solutions

1. Check the session key format '<platform>:<chatID>[:<userID>]' of the cron job's session
2. Trigger the platform once so a valid reply context exists, then re-run the job

When it happens

Trigger: Thrown at core/engine.go:1529 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chenhg5/cc-connect@4000b2338a (2026-09-06). Data as JSON: /api/errors/c099c35fee9724d1. Report an issue: GitHub.