List API for Advance List Stopped Returning Values

We rely heavily on List Single API that allows us to send over a list id to then return data from BBEM to populate in our ODS tables:

https://developer.sky.blackbaud.com/api#api=school&operation=V1ListsAdvancedByList_idGet

Last week, we ran into an issue where a report that hasn't been adjusted stopped working. We rebuilt it and now it's fine. Today, I noticed the same thing happening on a separate report.

@Stephen Boyle I remember an update in this section being mentioned last week during the Product briefing. Is this potentially something that is inadvertently being impacted with some future work?

I did submit a blackbaud case (020625912) to track it, but I really don't have the bandwidth to rebuild advance lists for multiple instances.

Answers

  • Hey @Lindsey Bryant. I haven't noticed the same issues with my extensions or usage of the List Single endpoint but did hear from one other person about this (coincidence?). I'm curious if @Stephen Boyle or Support has any specific insights for you. If I can try and help troubleshoot, feel free to email me here (nick@collarcityconsulting.com). Thanks!

  • @Nick Marchese thanks for the reply. I guess we will see what happens here. We have 3 BBEM instances, all of which have numerous advance list setup, so I'm really not looking forward to rebuilding them. I'm hoping we can get an answer soon especially since there is no other way to get this data out of BBEM and it's end of term for us.

  • I started experiencing issues with this same API around the same time. I have AirByte calling 2 lists and they are erroring, resulting in 429. I've opened a ticket with no luck so far. I also have an AWS script pulling a list in a Lambda function, it began failing around the same time. After some troubleshooting, I increased the timeout from 30 seconds to 90 seconds, and the list returns successfully (averaging 45 seconds for 1,700 rows of constituent data, about 1mb of data). This used to run in just a couple of seconds. I suspect my errors in AirByte may be related to increased response time on the list API, but the 429 error locks me out of troubleshooting it and there doesn't appear to be a way to reset it. (*My 429 is not rate limited, it is due to error, Input was fully read, but some streams did not receive a terminal stream status message. If the destination did not encounter other errors, this likely indicates an error in the source or platform. Streams without a status message). My BB case is 020638979.

  • Thanks, @Brent Halsey. I unfortunately haven't had much luck with support either. I did escalate the case yesterday and I'm hoping that we will make some progress here. My advance list returns around 30,000 rows in one of our instances and errors out. However, the exact same advance list with 80,000 rows returns with no issues. I'm going to try and add some pagination to help with the timing, but it's frustrating none the less. My case is 020625912.

  • I re-read this thread and realized you 'rebuilt' the list, and it started working, so I tried copying my lists that stopped working and using the copy, and that worked! Unsettling for sure, but at least back in business for now!

  • Glad that helped! Unfortunately for us, we have 3 instances of BBEM and some of our advance list are quite complex and need to match outlines exactly as we load them into our data warehouse.