Schedule issue

[sumwu]

We are using Veeam 7.0 yet we hit a problem using its API

From API, a Task ID is assigned to each job triggered by API call.
e.g. using API to edit the schedule of a VM, Task-ID 1 is assigned and the schedule is modified

However, when API calls the 101th time, Task-ID 101 is assigned and NO schedule is modified
Could anyone help?

[veremin]

As far as I remember, there used to be a sporadic problem in RESTful API with tasks starting from 100. However, if you follow the best practices and react promptly, closing tasks with delete request, you should not come across this issue. Thanks.

[sumwu]

With your recommendation, we have tried this but the issue persists

For example,

When task ID is less than 100,
We used a POST to edit a job  we used DELETE to remove the task (as recommended); the job has been edited

When task ID is greater than 100,
We used a POST to edit a job  we used DELETE to remove the task (as recommended); the job has NOT been edited

Are these the correct steps?

[veremin]

The main idea was not to reach numbers bigger than 100 by closing tasks in appropriate fashion. Anyway, it might be worth updating to v8 first, as there are many RESTful API improvements and enhancements introduced in that version. Thanks.

[Mardock]

Hi,
I have noticed the same issue with API v7.
I have upgraded to veeam API v8 but the issue never go away.

If I make DELETE request after Task has finished then the Task ID counter doesn't reset.
So when I reach a Task with an ID greater then 100 then the server response with a task that remains in the "running" state forever.

The only way to reset the task id counter is to reboot the veeeam API service.

Thanks,
Mardock.

[veremin]

I was slightly wrong when said that by closing tasks via delete request the counter should decrease. It's not the case.

Anyway, we've just checked the described behaviour and been unable to confirm the issue. So, please, open a ticket with our support team and provide its number here.

Thanks.