slowness of page loading + errors on all api calls

Brian Pugh

I noticed significant slowness in loading any API call (approx. 19 seconds to load a page). I am getting the same error no matter which API I call (see attached).

Lastly, I also use a very reliable addon to make a number of calls. It has worked without a hiccup for nearly a year; however, the last successful call occurred on 2022-07-18 23:44:41.

Chris Rodgers

Hi @Brian Pugh, we were seeing significant slowness Monday on our API Reference pages (especially when logged in), and we reached out to one of our vendors regarding an issue that we believed might have been contributing to the problem. They performed an upgrade on their side, and while we still usually see page loads in the 1-second range, I am occasionally seeing the slowness you're reporting. We'll reach back out to them.

As far as the API error response you're seeing--It's difficult to see in the screenshot, but the issue seems to be related to the Blackbaud Environment you're accessing. I'll send you a private message to learn more.

Brian Pugh

@Chris Rodgers
Thank you very much, Chris! (bpugh@ahschools.com)

Brian Pugh

@Chris Rodgers

Here is the full error message that I get on any api call.

Brian

{ "errors": [{ "message": "One PodLookup Service returned a 404. Check to make sure the mapping between the service type Blackbaud.EduLegacy.Service and the environment id p-iodq9lwA702c2JpvzVU8MQ exists in Blackbaud.One.PodLookup.DataService. (Parameter '_audienceName')", "error_code": -2147024809, "error_name": "One PodLookup Service returned a 404. Check to make sure the mapping between the service type Blackbaud.EduLegacy.Service and the environment id p-iodq9lwA702c2JpvzVU8MQ exists in Blackbaud.One.PodLookup.DataService. (Parameter '_audienceName')", "raw_message": "" }] }

Brian Pugh

@Chris Rodgers

Now getting this: Date: Thu, 28 Jul 2022 09:33:34 GMT
Content-Length: 268
Content-Type: application/problem+json

{
"status": 500,
"statusCode": 500,
"title": "Internal Server Error",
"message": "The SKY API service is currently unavailable - failed to resolve the environment audience.",
"detail": "The SKY API service is currently unavailable - failed to resolve the environment audience."
}

(Constituent

Address list (Single constituent)

Returns a list of addresses for a constituent.

Julian Daniel

@Brian Pugh I've noticed that the SKY API reference site (

)

Has been deathly slow for a couple weeks - upwards of 10-15 seconds for a page to load (this post took a good 10 seconds to load the link above).

Click an endpoint to research, and nothing happens for a very long time. This appears in my Chrome console:

DevTools failed to load source map: Could not load content for https://developer.sky.blackbaud.com/Modules/Portals.Web.Documentation/Scripts/es6-shim.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Error handling response: TypeError: self.processResponse is not a function
at chrome-extension://cmkdbmfndkfgebldhnkbfhlneefdaaip/js/notification.js:154:10

Chris Rodgers

@Julian Daniel I am still seeing that occasional slowness as well, especially on the first hit to that page (it was at least relatively snappy for me after that first hit). I'll add this to the support case with our vendor. Unfortunately, we are unable to resolve the 404 you're seeing on the page (it is a broken reference on our vendor's side). I will note it with the vendor, but it shouldn't affect page function. And I believe the other error you have there is unrelated to our Developer Portal--possibly a broken chrome extension?

Hey @Brian Pugh, sorry for the confusion. I sent you a private message here (on the community) Wednesday. You'll see the notification in the top-right of this page (the bell).

Julian Daniel

@Chris Rodgers after weeks of incredible slowness, today the site is spry and faster than it's ever been! I think whatever the problem was has been fixed!

Now, however, I'm seeing this:

POST https://sts.sky.blackbaud.com/oauth2/token 401

POST https://sts.sky.blackbaud.com/session/csrf 401

And yeah, the Chrome extension error was WhatRuns, which is supposed to tell me which platform is being used to generate the page,

Chris Rodgers

Glad you're seeing better load times, @Julian Daniel! We still have our support case open, so it's possible you'll still see an occasional dip in performance (hopefully temporary).

Those 401s you're seeing are async requests to check whether you're currently logged into you Blackbaud account; you'll see those responses if you aren't. 401 is the appropriate response from those endpoints in this case. Unfortunately, Chrome chooses to show a 401 response as an error in the console even though it is being appropriately accounted for client side. Definitely could be handy for troubleshooting, but I agree that it's ugly.