Error codes

The platform and the worker SDKs talk in numeric result codes attached to every message. These are the codes you set explicitly via setStopProcess(...), plus the ones the platform sets on your behalf when something goes wrong.

For language-specific enums see Node.js / ResultCode and PHP / ProcessDtoAbstract.

Success and routing (set by your code) #

Code	Name	Meaning
`0`	`SUCCESS`	Continue to the next node.
`1001`	`REPEAT`	Re-deliver this exact message to the same node.
`1002`	`FORWARD_TO_TARGET_QUEUE`	Route to a named successor instead of the default one.
`1003`	`DO_NOT_CONTINUE`	End this branch successfully.
`1006`	`STOP_AND_FAILED`	Mark the message as failed; goes to Trash after retries.

Batch (set by `ABatchNode` / `BatchAbstract`) #

Code	Name	Meaning
`1010`	`BATCH_CURSOR_WITH_FOLLOWERS`	Iterate again; emit accumulated items downstream now.
`1011`	`BATCH_CURSOR_ONLY`	Iterate again; hold items until iteration completes.

Platform-managed #

Code	Name	Meaning
`1004`	`LIMIT_EXCEEDED`	Limiter held the message back. The platform retries when a token is available.

Failure reporting (set by the platform) #

Code	Name	Meaning
`2001`	`UNKNOWN_ERROR`	Generic failure (e.g. uncaught exception).
`2002`	`INVALID_HEADERS`	Required headers were missing on inbound message.
`2003`	`INVALID_CONTENT`	Message body was not parsable.

HTTP status code conventions #

The worker REST API itself follows standard HTTP semantics:

Status	Meaning
`200`	The node ran. The body contains the outbound `ProcessDto`, which itself carries the result code above.
`400`	Malformed request from the platform (extremely rare; would indicate an SDK or platform bug).
`404`	Unknown component id; the worker doesn't have this connector / node / batch.
`500`	Uncaught exception inside the worker. The platform translates this to `UNKNOWN_ERROR`.