Start task
Launch the Task's background process (a `sym-kafkastream-app` child JVM, for the only known type `kafkastream-app`). Calling this again for a Task that is already running launches a **second** process and replaces the tracked handle for this name — the first process is not terminated and becomes untracked (it can then only be stopped by killing it outside the API). There is no guard against starting the same Task twice.
Launch the Task's background process (a sym-kafkastream-app child
JVM, for the only known type kafkastream-app).
Calling this again for a Task that is already running launches a second process and replaces the tracked handle for this name — the first process is not terminated and becomes untracked (it can then only be stopped by killing it outside the API). There is no guard against starting the same Task twice.
Authorization
SymetryMLAuth HMAC-SHA256 signature-based authentication: requests are signed with
your secret key and sent with the Customer-ID, Sym-date,
Authorization, Content-MD5 and sym-version headers.
See SymetryML REST API Security
for the signature algorithm and a complete example.
In: header
Path Parameters
User/Customer identifier
Task name (used as its identifier)
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/c1/tasks/kstream_task_0/start"{ "statusCode": 200, "statusString": "OK", "values": {}}{ "statusCode": 400, "statusString": "Customer [c1] has no Task [nosuchtask]", "values": {}}{ "statusCode": 500, "statusString": "Generic Exception [java.lang.Exception: Maximum number of task (4) already reached]", "values": {}}Get task status GET
Get the current runtime status of a Task's process. Only meaningful after the Task has been started via [Start task](/docs/api-reference/tasks/tasks-taskid-start-get) — the running-task registry is an in-memory map on the server, not persisted, so this reports `"not running"` both for a Task that was never started and for one that was running before the last server restart. `lastError` is misleadingly named — for a `kafkastream-app` task it's just the last line the process wrote to stderr, which routinely includes benign Kafka consumer-group rebalance `INFO` lines even while the task is healthy and `processIsAlive` is `"true"`. Don't treat a non-null `lastError` as proof the Task failed.
Stop task GET
Terminate the Task's running process, if any, but leave its registration in place — it can be started again later with [Start task](/docs/api-reference/tasks/tasks-taskid-start-get). If the process isn't currently tracked as running (never started, or the server restarted since), this is a silent no-op.