Transaction Distribution API call not returning

Stuart Herron

I have been trying to retrieve all of our transactions from the GET Transaction Distribution (List) API calls as we currently have a discrepancy between the number that have been retrieved in the past and the number that the API call now shows as a total count.

However, in the last couple of days I have been getting timeout messages (in the code) almost exactly 60 seconds after the API call has been made. I am only using the offset and limit parameters as I am trying to do a full refresh, I have made it to roughly 3.2 million records out of around 7.2 million but even if I drop the limit from the maximum 5000 to 100 the same issue is still occurring.

When I try to run the same parameters on the Sky API (Blackbaud) Website the request seems to send but never actually returns anything, again it seems to run for around a minute and then its almost as if the page is just refreshed but the auth token is still there.

Before

This is before I press send to make the API Call

During

This is after I have press sent, where it appears the API call is being processed

After

This is after the API call seems to have been processed, but there is no results below the original request, If there was an issue I would still expect a response from the API.

Has anyone else had anything like this? I would have expected an internal server error or something at least from the Try API on the website, I think the timeout message I am getting in the code is from the microsoft stack and not an actual response from the API.

Any help would be appreciated

Thanks,

Stuart

Chris Rodgers

Hey Stuart,

Are you still having this issue? I do these these failing requests from your account and from another account at your organization last week. I also see successful requests from both accounts later on 10/14 and over the next couple days. I agree, the responses we have logged are strange in that they don't indicate a timeout, but I agree that it has every indication of appearing as one. We also have our own indicators for when a request gets canceled on the client's (your) end, and I don't see that either. I'll pass this along internally here; however, if you see this again (or if it is still happening), feel free to work through your Blackbaud support channels to get to the issue tracked and raised up formally.