runstart

type Component ¶

type Component struct{}

func (t *Component) GetInfo() module.ComponentInfo

func (t *Component) Handle(ctx context.Context, handler module.Handler, port string, msg interface{}) module.Result

func (t *Component) Instance() module.Component

func (t *Component) Ports() []module.Port

type Context ¶

type Context any

type OutMessage ¶ added in v0.7.18

type OutMessage struct {
	Context Context `json:"context" configurable:"true" title:"Context" description:"Passthrough — the message, unchanged"`
}

Component is the front door into durable execution. It starts a durable run, fires the chain on Out WITHOUT waiting for it (the emit returns as soon as the first hop is durably stored), and then emits {runID} on Started — which, wired back to an http_server response, gives the HTTP caller an immediate handle to poll while the run continues in the background, surviving pod restarts and migrating across replicas.

Place it on a CLASSIC (non-durable) node between the trigger and the durable chain. Downstream nodes need no labels: every hop emitted under the run identity rides the durable path. OutMessage keeps the passthrough Context under a `context` key so a downstream edge reads $.context.<field> — the mid-chain convention (same as the router, pod_logs_get, llm_tools). Was emitting the raw Context value at root.

type Request ¶

type Request struct {
	Context Context `json:"context" configurable:"true" title:"Context" description:"Payload to send into the run"`
}

type Started ¶

type Started struct {
	Context Context `json:"context,omitempty" configurable:"true" title:"Context"`
	RunID   string  `json:"runID" title:"Run ID" description:"The run's id — check it with Run Status"`
}