Closed grahamimac closed 4 years ago
Note this could very well be the error I'm running into (e.g., columns aren't matching meaning the JSON doesn't have a consistent # of keys across the list), so would love to have you look into it on your end.
Yes, this is almost certainly the same issue, but I will dive into a bit to try to give you some more context. Problem is this will occur at random times on the API back end, so nearly impossible to fully replicate. But with 512 pages maybe it's just good odds it will happen on at least one of them. If you check out the repo for the API itself you will see an issue from me that has some more detail on this behavior, albeit on a different endpoint.
I was able to replicate this across packages, so closing this here and moving discussion to your comment. No need to follow up on this further. Thanks Kyle.
@khueyama Getting an error when running the following. I need to run this to check against a priority error I'm getting elsewhere in the portal to isolate it, so this is top priority for me. As soon as you can get to it the better. Thank you!
Runs and all API calls execute (seems successfully). Then this error
Session info: