Is it possible to have multiple

1984 Ford Laser · 2025-11-24T22:13:21.223Z

Is it possible to have multiple `waitForEvent()`s running at the same time for a single Workflow instance? I am starting a Workflow when a user begins uploading a series of files to R2, and using R2 Event Notifications to notify the Workflow when each file is complete. I don't think I can guarantee the order of upload so I would prefer to wait for all files to be uploaded at the same time. Otherwise I will use a single `waitForEvent` that will re-trigger another `wait..` until all required files are uploaded

A

avenceslau•11/25/25, 8:51 AM

You should be able to do something like

Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, { type: key, timeout: "24 hours"})))

Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, { type: key, timeout: "24 hours"})))

Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, { type: key, timeout: "24 hours"})))

Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, { type: key, timeout: "24 hours"}))), and your queue consumer can sendEvent with the file key.

Aavenceslau You should be able to do something like `Promise.all(r2ObjectKeys.map((key) => s...

1

1984 Ford LaserOP•11/25/25, 9:43 AM

Legend thank you I'll give that a try tomorrow

1

1984 Ford LaserOP•11/25/25, 9:23 PM

Would this be put in a distinct

step.do()

step.do()

step.do()

step.do() or just in the main

run

run

handler itself?

A

avenceslau•11/26/25, 8:40 AM

On the run handler

1

1984 Ford LaserOP•11/26/25, 11:18 AM

Got it working in the end, I was running into the issue with non-accepted characters in the waitForEvent type while trying to figure this out

A

avenceslau•11/26/25, 12:46 PM

Glad you got it working! I will see what we can do about supporting . on event types

1

1984 Ford LaserOP•11/30/25, 2:06 AM

When using

Promise.all(...)

Promise.all(...)

Promise.all(...)

Promise.all(...), the instance tracking doesn't seem to persist all

waitFor...

waitFor...

waitFor...

waitFor... steps forever for some reason. It'll hang onto the event response times for some amount of time, but then eventually will disappear. I definitely want to track these steps, should I be doing that separately or is something else wrong here?

A

avenceslau•11/30/25, 1:21 PM

We can have a look at that during the week. Do you mind sharing the code? DM is fine if you prefer

1

1984 Ford LaserOP•11/30/25, 8:29 PM

async run(event, step) {

        
        const r2ObjectKeys = await step.do('logUpload', async () => {
            
            console.log(event.payload);
            let r2FileKeys = [];
            for (let file of event.payload.files) {
                r2FileKeys.push(`${file.path}${file.name}`);
            }
            console.log(r2FileKeys);
            
            return r2FileKeys;
        });

        await Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, {type: key.replace(/[^A-Za-z0-9_-]/g, ''), timeout: "24 hours"})));
}

async run(event, step) {

        
        const r2ObjectKeys = await step.do('logUpload', async () => {
            
            console.log(event.payload);
            let r2FileKeys = [];
            for (let file of event.payload.files) {
                r2FileKeys.push(`${file.path}${file.name}`);
            }
            console.log(r2FileKeys);
            
            return r2FileKeys;
        });

        await Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, {type: key.replace(/[^A-Za-z0-9_-]/g, ''), timeout: "24 hours"})));
}

async run(event, step) {

        
        const r2ObjectKeys = await step.do('logUpload', async () => {
            
            console.log(event.payload);
            let r2FileKeys = [];
            for (let file of event.payload.files) {
                r2FileKeys.push(`${file.path}${file.name}`);
            }
            console.log(r2FileKeys);
            
            return r2FileKeys;
        });

        await Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, {type: key.replace(/[^A-Za-z0-9_-]/g, ''), timeout: "24 hours"})));
}

async run(event, step) {

        
        const r2ObjectKeys = await step.do('logUpload', async () => {
            
            console.log(event.payload);
            let r2FileKeys = [];
            for (let file of event.payload.files) {
                r2FileKeys.push(`${file.path}${file.name}`);
            }
            console.log(r2FileKeys);
            
            return r2FileKeys;
        });

        await Promise.all(r2ObjectKeys.map((key) => step.waitForEvent(key, {type: key.replace(/[^A-Za-z0-9_-]/g, ''), timeout: "24 hours"})));
}

O

Olga Silva•12/2/25, 1:50 PM

Hey @1984 Ford Laser thank you for raising this! We're fixing this atm

O

Olga Silva•12/3/25, 11:17 AM

This is fixed now @1984 Ford Laser can you check from your side? Thanks!

1

1984 Ford LaserOP•12/3/25, 11:19 AM

!remindme 12h check this

F

Flare•12/3/25, 11:19 AM

:zep_check: I will remind you in 12 hours at Dec 3, 2025 at 23:19 UTC

F

Flare•12/3/25, 11:19 PM

Reminder for @1984 Ford Laser: check this
Set December 3, 2025

1

1984 Ford LaserOP•12/4/25, 9:13 PM

Looks like we're all good! Thank you guys

Similar Threads

Similar Threads

Similar Threads