Schedules can't process long AI requests

[SamyPesse]

Describe the bug
When using the schedule feature to "debounce" processing some async workflow, the execution is limited to only 30s, or it'll fail with:

IoContext timed out due to inactivity; waitUntil tasks were canceled without completing.

It happens as we have to void a promise instead of await it in the scheduled function, as otherwise it fails because of the limit of blockConcurrencyWhile:

A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset.

Expected behavior
I'm not sure how to work around this problem; it looks like removing blockConcurrencyWhile might help, but I'm not sure.

Version:
We are using a old version 0.0.76, but it also happens when upgrading to latest version 0.2.17.

[whoiskatrin]

Highly recommend updating the version to the latest, simply because the old version you are using wasn't very stable and lacks a lot of features.

Re: issue, will look into this

[threepointone]

We probably don't need bcW where we call the schedule callback, can't recollect a good reason for it

[deathbyknowledge]

We might be able to remove the bcW and the manual this.alarm call from the constructor. If the DO is waking up because of an alarm, alarm() should run afterwards regardless which will pull any pending schedule.