Tencent/WeKnora · error

bind owned remote sandbox: %w

Error message

bind owned remote sandbox: %w

What it means

This error wraps a failure from the binding store's Create when the lifecycle, having connected to a recovered orphaned sandbox, tries to record the SessionSandboxBinding for it. If persisting the binding fails, the recovered handle is abandoned and 'bind owned remote sandbox: %w' is returned, since reusing the sandbox without a durable binding would break future resolution.

Source

Thrown at internal/sandbox/session_lifecycle.go:328

			if CanReplaceRemoteBinding(err) {
				continue
			}
			return nil, false, fmt.Errorf("connect owned remote sandbox: %w", err)
		}
		if err := l.validateHandle(handle, summary.ID); err != nil {
			return nil, false, err
		}
		if err := l.cleanupOwnedDuplicates(ctx, summaries, summary.ID, metadata); err != nil {
			return nil, false, err
		}
		templateID := summary.TemplateID
		if templateID == "" {
			templateID = l.createRequest.TemplateID
		}
		binding := l.newBinding(key, summary.ID, templateID, summary.StartedAt)
		created, err := l.bindings.Create(ctx, key, binding)
		if err != nil {
			return nil, false, fmt.Errorf("bind owned remote sandbox: %w", err)
		}
		if created {
			return handle, true, nil
		}
		winner, err := l.connectWinner(ctx, key)
		if err != nil {
			return nil, false, err
		}
		return winner, true, nil
	}
	return nil, false, nil
}

func (l *remoteSessionLifecycle) createAndBind(
	ctx context.Context,
	key SessionSandboxKey,
) (RemoteSandboxHandle, error) {
	request := l.createRequest

View on GitHub (pinned to 988cbb0330)

Solutions

1. Check the binding store's availability and the wrapped error for backend-specific detail
2. Verify write permissions on the binding storage backend
3. Retry resolution once the store recovers — the orphan will be re-discovered and rebound
4. Inspect recent schema/migrations of the binding store for incompatibilities

Example fix

// before
created, err := bindings.Create(ctx, key, binding) // fails: store unavailable
// after
created, err := bindings.Create(ctx, key, binding)
if err != nil {
    // backoff and retry once before giving up
    time.Sleep(backoff)
    created, err = bindings.Create(ctx, key, binding)
}

// verify the binding store is writable before starting resolution
if err := bindings.HealthCheck(ctx); err != nil {
    return fmt.Errorf("binding store unavailable: %w", err)
}

handle, err := session.Resolve(ctx, key)
if err != nil && strings.HasPrefix(err.Error(), "bind owned remote sandbox:") {
    err = retryWithBackoff(ctx, 3, func() error { handle, err = session.Resolve(ctx, key); return err })
}

When it happens

Trigger: l.bindings.Create(ctx, key, binding) returns an error after a successful Connect during recoverOwnedSandbox — the binding store's backend (database, KV, lock store) is unavailable, the write conflicts, permissions are insufficient, or the record schema changed.

Common situations: Binding-store database down or migrated; concurrent writers causing store-level conflicts; permissions revoked on the binding table/bucket; metadata (template ID fallback to createRequest.TemplateID) producing an invalid record; disk/full or quota errors on the store.

Related errors

• create sandbox binding: %w
• save: %w
• failed to write file: %w
• failed to delete file from OSS: %w
• register stored resource: %w

AI-assisted analysis of Tencent/WeKnora@988cbb0330 (2026-09-02). Data as JSON: /api/errors/eae5b908ca9ac4ec. Report an issue: GitHub.