I'm trying to use the REST API to automatically refresh all of my datasets after their data sources are updated every morning. I've written a .NET program that will get the list of Datasets, check who owns them, if it's not me, take ownership and set the Gateway to our on-premises Gateway, and then run the refresh for that Dataset. At most, each Dataset could require up to three API calls (not counting the original call to get the list of Datasets).
My problem is that after I run the first three API calls, ALL subsequent calls fail with the message "The operation has timed out". This was with the default timeout of 100 seconds on the WebRequest, and it happens when stepping through the program.
It doesn't matter what the first three calls are OR what the next call is that fails (it could be a call to take ownship, or set the Gateway, or run a refresh... makes no difference). For example, if the first two Datasets are already owned by me, it will fail on the attempt to take ownership of the third dataset (i.e. the fourth API call after Get Dataset call and two refresh calls). If the first one isn't owned by me, it will fail on the step to refresh it after taking ownership (i.e. the fouth API call after Get Dataset list, Take ownership, and Set Gateway). Etc. etc.
I've tried several differet scenarios and they all play out the same way: after I make my third call, no matter what it is, all the rest time out.
If I stop debugging my program and start it up again, I can do three more calls until it fails again, so it's not a "daily limit" or anything like that. I've also waited long amounts of time in between calls (particularly when I was still wokring on the program), so it's not like I'm running the calls too close together.
Does anyone know what might be causing this?
