Is it a few minutes from the last retry or the original invocation?
Is it a few minutes from the last retry or the original invocation?

waitForEvent function (https://www.inngest.com/docs/features/inngest-functions/steps-workflows/wait-for-event), which I know CF doesn't have, but wondering if there are other creative ways that are not too hacky to support this kind of functionality with CF.waitForEvent steps or events as entrypoint (focus on the "for the moment" onmessage handler with a promise that could be awaited in the step https://api.slack.com/apis/socket-modestep.do supposed to return? If I return anything at all from it, it causes the workflow to throw an exception after finishing successfully, every time, and I can't figure out what I'm doing wrongfunctions/[[path]].ts file that looks like: 

remix vite:dev on port 3000wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.tsworker.ts should be ESM-based for Cloudflare Workers. wrangler dev enables you to develop queues, crons, and workflows within workerd environment instead of NodeJS.getPlatformProxy() doesn’t work with workflows. If you have [[workflows]] in wrangler.toml, Miniflare will refer to it, resulting in the errorType instantiation is excessively deep and possibly infinite. in a step. I don't think it's a very complex type being returned
scheduled handler for thisvar htmlRewriter = new HTMLRewriter();
var title = '';
var description = '';
var favicon = '';
var ogImage = '';
htmlRewriter.on('title', {
text: (text) => {
title = text;
}
});
htmlRewriter.on('meta[name="description"]', {
element: (element) => {
description = element.getAttribute('content');
}
});
htmlRewriter.on('link[rel="icon"]', {
element: (element) => {
favicon = element.getAttribute('href');
}
});
htmlRewriter.on('meta[property="og:image"]', {
element: (element) => {
ogImage = element.getAttribute('content');
}
});
var content_response = new Response(html, {
headers: {
'Content-Type': 'text/html',
},
});
await (await htmlRewriter.transform(content_response)).text();
console.log('meta data', { title, description, favicon, ogImage });
return { title, description, favicon, ogImage };const {id} = await WORKFLOW.create();
console.log(id) // RpcProperty {}for (const { weekStart, weekEnd } of weeklyIntervals) {
const events = await step.do(
`fetchMeetings for ${weekStart} - ${weekEnd}`,
{ retries: { limit: 3, delay: 2000 } },
async () => {
const response = await fetch(
`https://www.googleapis.com/calendar/v3/calendars/primary/events?timeMin=${weekStart}&timeMax=${weekEnd}&orderBy=startTime&singleEvents=true`,
{
headers: { Authorization: `Bearer ${accessToken}` },
}
);
if (!response.ok) throw new Error("Failed to fetch events");
const data = await response.json();
return data.items.map((event: { summary: string }) => event.summary);
}
);
// Log summaries for this week
events.forEach((summary: string, index: number) =>
console.log(`Event ${index + 1} on week ${weekStart} - ${weekEnd}: ${summary}`)
);
}waitForEventwaitForEventonmessagestepstep.do[ERROR] Your Worker depends on the following Workflows, which are not exported in your entrypoint file: DemgEventWorkflow.
You should export these objects from your entrypoint, build/worker/index.jsfunctions/[[path]].tsimport { createPagesFunctionHandler } from "@remix-run/cloudflare-pages";
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore - the server build file is generated by `remix vite:build`
// eslint-disable-next-line import/no-unresolved
import * as build from "../build/server";
export const onRequest = createPagesFunctionHandler({ build });remix vite:devwrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.tsworker.tsworkerdgetPlatformProxy()[[workflows]]Type instantiation is excessively deep and possibly infinite.scheduled