Understanding Discrepancies in Screener Results #215
Unanswered
Hiddenleaf07
asked this question in
Q&A
Replies: 1 comment
-
|
@Hiddenleaf07 - That's most likely because many a times for some of the tickers, we get empty datasets. So, those tickers get ignored, especially during market hours. Post market-hours, the download job runs and saves all tickers' data in a pickle, but even during that download job, if we received empty data for those tickers, the results will still vary even after running post-market-hours. This happens most frequently because we hit HTTP 429 status codes (rate-limits). From your local machine, when you request, you may receive data for those missing stocks because your IP was not rate-limited. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Recently, I deployed PK Screener on GitHub Codespaces. However, I've noticed slight discrepancies between its results and those shared in the public channel, even after testing post-market hours. I'm getting extra results compared to the public channel.
Beta Was this translation helpful? Give feedback.
All reactions