I tried calling the second from the first via a fetch on another domain, and that worked, but I encountered a 525 error on a subfetch to a 3rd-party API inside it (525 is an SSL handshake error - the 3rd-party call succeeds from a scheduled worker, but fails on SSL handshake when run from a route).
Is there an easier way to run these or do I need to figure out a way around the 525?
Is it surely there is no Firewall Events or some other possible Security which could potentially block your requests?
Useful articles about 525 error you are encoutering so far for now:
Particularly, correctly setup the SSL for your domain at first sight and possibly going step-by-step to troubleshoot the SSL handshake issue?
Here is a way to re-check if you correctly setup the SSL for your domain with Cloudflare:
In case you do not have an SSL certificate, you can use Cloudflare SSL, if so, kindly make sure you follow the instructions as follows on the below article to setup an SSL certificate using Cloudflare CA Origin Certificate:
I don’t think this has anything to do with SSL on my domain (which has been set up correctly), as the call to the 3rd-party API is the part that is failing. The 525 error, in this case, is ambiguous as I read somewhere that workers can throw this inside a fetch to an external domain too.
What I was really wondering was if there was a way to trigger a scheduled task from inside a scheduled task.
In the meantime, I think I am just going to work around the 525 by proxying it.