Hey guys.
To anyone using LCAC's loan scanning function - are a significant portion of your loans coming up as "undefined"?
I just noticed this today when I scanned my loans. Approx 50% of my loans are now showing "undefined" as their FICO, and the links to the loans on lendingclub's website are broken.
Is there a fix? Did I break something?
I updated to the latest LCAC version - problem continues!
I think LendingClub is throttling the number of Loan Performance pages one can look at over some period of time.
When I would click on of the error links to open the Loan Performance page, LendingClub would return with their Temporarily Unavailable" maintenance web page, although other pages would still work.
I thought I slowed down the scan below the limit, but it was just trial and error. (I am running a scan at the moment on my machine and it seems to be going OK.)
Can you open one of the links, and keep it open, then try loading it again after a few minutes? This would help to make sure the link is not malformed or something.
I noticed the same thing. It would scan about 30 then stop working. I'd get an error message when I tried to open it manually. Thanks for the update.
The "temporarily unavailable" page on the LC website seems to be permanent. It doesnt seem to fix itself after an hour.
Actually, as I was clicking through them all, I noticed that some of them got fixed and some didnt.
Can you recommend how I edit the code to slow the scan down even more?
Awesome. it seems to have fixed it.
So LC has definitely added some new throttling today? It wasn't just temporary LC issues? Strange that of all things, they don't want you looking at too many of your own loans.
yojoakak- If you work out the exact timing restrictions they have in place (and if they're going to stay,) you may want to change it so the time is measured from start of fetch to next start of fetch rather than a fixed sleep time from end of one to start next. On a poor connection like mine I could eat up the requisite time just waiting on one response. Otherwise someone's luck with the default settings is going to depend on how fast things happen to go for them that day on that machine.
I have my program set to a 1000ms delay, and if there are errors encountered, wait 5000ms before a retry. Seems to work consistently.
I assume you guys are talking about this?
http://userscripts.org/scripts/show/103295
I've made some changes to the script.
There is now a dropdown where you can choose the delay. I set the default to 3 seconds, but you can try making it go faster.
I also added a timestamp to the URL to try and bypass any caching that might be going on in the browser on the off chance this has something to do with it.