Tasks are activated by default which means that triggers defined for a task are able to start its execution automatically. Deactivated tasks can be only executed manually or by the Next Task action.
See also: /<TaskID>/activate
Requests deactivation of the task.
# Request # Use user:password for authorization GET /api/taskplanner/4w8yavnk046debwrwkcg4dbqh/deactivate HTTP/1.1 Authorization: Bearer VGhpcyBpcyBqdXN0IGEgZGVtbyBhY2Nlc3MgdG9rZW4u # Response - Task is deactivated HTTP/1.1 200 OK Content-Type: application/json Content-Length: <CONTENT LENGTH> "4w8yavnk046debwrwkcg4dbqh"
# Request # Use user:password for authorization GET /api/taskplanner/4w8yavnk046debwrwkcg4dbqh/deactivate HTTP/1.1 Authorization: Bearer VGhpcyBpcyBqdXN0IGEgZGVtbyBhY2Nlc3MgdG9rZW4u # Response - Task does not exist HTTP/1.1 404 Not Found Content-Type: application/json Content-Length: <CONTENT LENGTH> { "error": "An answer could not be found: Task does not exist, taskID = 4w8yavnk046debwrwkcg4dbqh" }
# Browser access http://127.0.0.1:9000/api/taskplanner/4w8yavnk046debwrwkcg4dbqh/deactivate # Shell access using curl curl -LsH "Authorization: Bearer <access_token>" "http://127.0.0.1:9000/api/taskplanner/4w8yavnk046debwrwkcg4dbqh/deactivate" # Shell access using curl using username and password curl -Lsu username:password "http://127.0.0.1:9000/api/taskplanner/4w8yavnk046debwrwkcg4dbqh/deactivate"