Hello rois-investments,

I have deployed an update to the Actor, which changes the configuration to hopefully increase the reliability.

Could you please check if the issue persists?

Unfortunately, some requests still might fail on 403, as this is not possible to avoid completely.

Yes the issue persists. I even made list of the stocks that are getting constantly blocked (after 3 iterations) and saved them down to a new excel, then ran them at a later time, and they ALL still got blocked.

Perhaps this means that security is more tight on some tickers than others?

Is their a way to use residential proxies here? Finding a proxy to use that doesn't get blocked would be key- any ideas?

Or perhaps this below can be a solution according to ChatGPT

Implementing Delays and Request Throttling: Actionable Step: Again, check the Apify actor's input settings. Some scraper actors allow you to configure delays between requests or limit the number of concurrent requests. Look for parameters like "Delay between requests", "Max concurrent requests", "Rate limiting", etc.

Yes, I believe this is mostly a proxy issue. I have deployed another update allowing to set a proxy group in the input. Could you please try to run the Actor with residentials?

Alternatively, if this doesn't help, could you please share an example run with me?

Yes, ran again with residentials.

Still running into issues retrieving the same stocks that were blocked before the residential proxy was created.

BUT, when I run one of the blocked stocks not with the API, but just on manual run page you have created for sample runs, the retrieval works perfectly- why the discrepancy?

A sample of what I would be running below and what is seeing errors - happy to take this offline if needed...