We have a cron job in our system which triggers an API, initiating a function. This function iteratively makes a substantial number of API requests, often in excess of 100. All api routes are edge functions.

These requests subsequently initiate edge functions, resulting in further requests, and eventually leading to updates in our MySQL database.
Under asynchronous operation, this entire process would typically exceed 25 seconds. When run synchronously, the calls originating from the initial loop cease after 25 seconds. This is perplexing because the loop should have instructed all 100+ edge functions to initiate, regardless of whether the initial cron job has concluded. The result of the cron is we get about half of the data we expect to get before it gives up on the initial list.

The puzzling part is why the calls cease after the 25-second mark, even though they should technically operate independently of the initial cron job's lifecycle. Could you help shed light on this?"