Tencent/WeKnora · error

script execution failed

Error message

script execution failed

What it means

Sentinel ErrExecutionFailed returned when a script executed in the sandbox exits with a non-zero status or otherwise fails at runtime. The ExecutionResult (stdout/stderr/error fields) carries the details; this sentinel just classifies the failure for callers.

Source

Thrown at internal/sandbox/sandbox.go:104

	DefaultCubeSandboxTTL = 30 * time.Minute
	// DefaultCubeHTTPTimeout bounds a single HTTP call to the CubeAPI
	// (excluding user script execution which has its own per-call timeout).
	DefaultCubeHTTPTimeout = 30 * time.Second

	// DefaultE2BSandboxTTL matches the E2B SDK's built-in default so an
	// unset E2BSandboxTTL still yields a valid sandbox lifetime.
	DefaultE2BSandboxTTL = 5 * time.Minute
	// DefaultE2BHTTPTimeout bounds a single HTTP call to the E2B API.
	DefaultE2BHTTPTimeout = 30 * time.Second
)

// Common errors
var (
	ErrSandboxDisabled   = errors.New("sandbox is disabled")
	ErrTimeout           = errors.New("execution timed out")
	ErrScriptNotFound    = errors.New("script not found")
	ErrInvalidScript     = errors.New("invalid script")
	ErrExecutionFailed   = errors.New("script execution failed")
	ErrSecurityViolation = errors.New("security validation failed")
	ErrDangerousCommand  = errors.New("script contains dangerous command")
	ErrArgInjection      = errors.New("argument injection detected")
	ErrStdinInjection    = errors.New("stdin injection detected")
)

// Sandbox defines the interface for isolated script execution
type Sandbox interface {
	// Execute runs a script in an isolated environment
	Execute(ctx context.Context, config *ExecuteConfig) (*ExecuteResult, error)

	// Cleanup releases sandbox resources
	Cleanup(ctx context.Context) error

	// Type returns the sandbox type
	Type() SandboxType

	// IsAvailable checks if the sandbox is available for use

View on GitHub (pinned to 988cbb0330)

Solutions

  1. Inspect the returned result's Stderr and Error fields for the root cause
  2. Fix the script's runtime errors (missing packages, bad syntax, unhandled exceptions)
  3. Retry only if the failure is transient (e.g. provider hiccup)
  4. Report script output back to the user/agent so it can self-correct
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at internal/sandbox/sandbox.go:104 when the library encounters an invalid state.

Common situations: See trigger scenarios.


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