The GET /tasks route can now accept a reverse boolean query parameter set to false by default.
If set to true, then the tasks will be returned in reversed order (the oldest first).
List all the new or updated telemetry
| Name | Description | Example |
|---|---|---|
| e.g. infos.log_level | e.g. “value of --log-level” | e.g. “debug” |
No new telemetry, the reverse parameter can only be used from the GET /tasks route, which doesn’t send any telemetry.
If the reverse parameter contains anything else than true or false an error is returned with the error code invalid_task_reverse.