RULES - how to manage scheduled execution time using API

Hi All,
I'm trying to manage RULES using API endpoints.
I'm using Elasticsearch version 8.14.3.
I'm using Dev Console and "kbn:/api/alerting/rule" endpoint.

I've different rules to set and my desired goal is to set the next execution time.
My rules execute every 24 hours.
I saw that the next execution time ("next_run" value) is calculated from the "updated_at" value.

As an example:
GET kbn:/api/alerting/rule/432d0510-b9e4-11ee-acfb-41e2c480596b

return:

{
  "id": "432d0510-b9e4-11ee-acfb-41e2c480596b",
  "consumer": "discover",
  "schedule": {
    "interval": "24h"
  },
  

[::::REDACTED::::]


  "created_at": "2024-01-23T11:40:53.343Z",
  "updated_at": "2024-09-03T09:52:16.850Z",


[::::REDACTED::::]


  "scheduled_task_id": "432d0510-b9e4-11ee-acfb-41e2c480596b",
  "execution_status": {
    "status": "active",
    "last_execution_date": "2024-09-03T09:52:21.386Z",
    "last_duration": 747


[::::REDACTED::::]


  "next_run": "2024-09-04T09:52:21.308Z",


[::::REDACTED::::]


}

Focusing on the interesting attributes/values:
"next_run": "2024-09-04T09:52:21.308Z" is calculated from

"updated_at": "2024-09-03T09:52:16.850Z"

augmented by

"schedule": {
  "interval": "24h"
}

I searched for how to chamge/manage the scheduled task using the
"scheduled_task_id": "432d0510-b9e4-11ee-acfb-41e2c480596b"

but I didn't find a way to get access to this task and to its properties.

I just found the "pity" solution to make changes to a rule at a specified time in order to change the scheduled time (+24h from the time of the changes applied), but it has lot of inefficiencies , constraints and not in a scalable way...

  1. it cannot be used for setting a precise scheduled time
  2. the same scheduled time cannot be applied to different rules because of the time required to apply changes to each rule

Which is the best practise to manage scheduled time for rules?
How to manage the scheduled task referenced in "scheduled_task_id" ?

Thanks a lot!
M-CD

Added elastic-stack-alerting