This has been observed with the colab.

https://colab.research.google.com/drive/17fhUhpukiOXwFdP88i9q2tRZXfs-HMbF#scrollTo=SZz_DUz5AQIi

Create 3 campaigns, add them in one state. Start the process. For updating, the way it is now, we update with a new spent every time step that is 600. However, given that the budget for that time step is 666, the spent should be around a half of 666 (since there are two time steps per day) and not that much as it is given (600). Because of this, maybe it could be interesting that the API gives an error when updating with such these big spent values. idk even if i would call it as an error but in any case i point it out here in issues for the future

I think it would be better to update remaining budget by substracting the total spent in the last time step and not by substracting the assigned budget in last time step. It is important because it can help to avoid problems with overspend, apart from adjusting more efficiently budget per time step

Sometimes it has occurred to me that I tried to upload a campaign with a new spent value but if it was coincident with an existing one in the spent list, it was not added to it. Say this just to add it here and take into account for the future because I m still not very certain why this happens and how.

There were three campaigns at the beginning, I deleted two of them with the method 'Delete Campaigns'. If I try out 'Get Campaigns' I get it correctly, only the one I expect. The problem comes out when I try out 'Get State', it gives the first three initial campaigns with no updates coming from having deleted these two campaigns. Something similar if I 'Delete State'. Once done this, if I 'Get Campaign' I receive the one campaign left but I should receive none since the state was deleted.

I created 4 campaigns, I included them in one state, I call /next, this is what happened

I create 3 campaigns, I include them in one same state, i call /next for the 1st time step, I update every campaign with new spent plus new conversion value (everything okay so far), BUT now I call /next again, this is what happens