Hi @...

The last 3 years it was possible to activate a SLA with a ticket update via API and a empty end user comment body:

{
"ticket": {
"comment": {
"body": "",
"author_id": 376666831978,
"public": true
}
}
}

Since july 29 nothing happens anymore. Before the change, the SLA was started with such API request. See this screenshot:

We used this workflow for quite different cases, e.g.
- Starting the SLA for proactive tickets
- Starting the SLA after adding internal comments
- Restarting the SLA because only one public comment was sent as an intermediate message, but a follow-up message must be sent to the customer within a new SLA.

All these cases were realized with a trigger + webhook + the API call above.

So we have to know why was this changed? What are the new workarounds to realize the cases shown?