K
AKA
M
terminateAll here, although I would suggest redeploying the code that is spawning them to at least stop the initial run. cc @Seekerdasbatatas
S
vitest-pool-workers to not crash with Workflows: https://github.com/cloudflare/workers-sdk/pull/8208, hopefully gets merged really :soontm: - you should be able to do some e2e testing with this, but we have more utils to properly test steps in our roadmap.
J
DKMKDDMMK
FF
US
, could you give me your account id so I can investigate further?U
adbf3651ede24f0e60bc37f80673f51f, Thanks!
BBBUA call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset 
U
S
SKK
B
KKKK
R
F
B
createInstance. When I ran npm run cf-typegen from my nuxt app, it made MY_WORKFLOW a Fetcher type, not Service. Maybe I did something wrong but I'm not sure?
Ac.env.COVE_WORKFLOW_VIDEO.create({ I think it is saying that the actual workflow is not bound.
A
H
IIJ
JYA
.create(), .status(), .terminate() from multiple workers?Ato call into Workflows from other Workers scripts.terminateAllvitest-pool-workersadbf3651ede24f0e60bc37f80673f51fA call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset{
message: "TypeError: Cannot read properties of undefined (reading 'fetch')",
details: "TypeError: Cannot read properties of undefined (reading 'fetch')\n" +
' at null.<anonymous> (file:///****/node_modules/.pnpm/@microlabs+otel-cf-workers@1.0.0-rc.40/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:243:80)\n' +
' at Object.apply (file:///****/node_modules/.pnpm/@microlabs+otel-cf-workers@1.0.0-rc.40/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:211:19)\n' +
' at proxyHandler.apply (file:///****/node_modules/.pnpm/@microlabs+otel-cf-workers@1.0.0-rc.40/node_modules/@microlabs/otel-cf-workers/src/wrap.ts:33:19)\n' +
' at fetch (file:///****/node_modules/.pnpm/@supabase+supabase-js@2.48.1/node_modules/@supabase/supabase-js/src/lib/fetch.ts:15:42)\n' +
' at null.<anonymous> (file:///****/node_modules/.pnpm/@supabase+supabase-js@2.48.1/node_modules/@supabase/supabase-js/src/lib/fetch.ts:46:12)\n' +
' at Generator.next (<anonymous>)\n' +
' at fulfilled (file:///****/.wrangler/tmp/dev-QyRdTX/index.js:78978:24)',
hint: '',
code: ''
}""error":{"name":"WorkflowFatalError","message":"The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"}"throw new NonRetryableError('PDF not found');createInstancenpm run cf-typegenMY_WORKFLOWFetcherServicec.env.COVE_WORKFLOW_VIDEO.create({.get(
"/workflow",
validator(
"query",
z.object({
videoId: z.string().min(1),
instanceId: z.string().optional(),
}),
),
describeRoute({
tags: ["Video"],
}),
async (c) => {
const organization = c.get("organization");
const { instanceId, videoId } = c.req.valid("query");
const video = await db(c.env.COVE).video.findUnique({
where: { id: videoId, organizationId: organization?.id },
});
if (!video) {
return c.json({ error: "Video not found" }, 404);
}
if (instanceId) {
const instance =
await c.env.COVE_WORKFLOW_VIDEO.get(instanceId);
return c.json({
status: await instance.status(),
});
}
// Spawn a new instance and return the ID and status
const instance = await c.env.COVE_WORKFLOW_VIDEO.create({
params: {
key: video.key,
},
});
return c.json({
id: instance.id,
details: await instance.status(),
});
},
).create().status().terminate()to call into Workflows from other Workers scripts.// Inside the workflow (Maybe it could have some timeout option to fail the workflow if the event never comes within a timeframe)
const payload = await step.waitFor("event_name", "10 minutes")
// And outside the workflow, having the ability to check what event is being waited on would be great to avoid race conditions leading to stuck workflows
if("event_name" === await workflowInstance.waitedOnEvent()){
await workflowInstance.send("event_name", /* Optional payload */)
}
// And for events that we just want to queue for whenever they come up and don't care that the workflow will start waiting for them we can simply send them
// This would be useful for cases where multiple webhook events that we are interested in might come out of order so that we wouldn't need to care about when we send them to the workflow
await workflowInstance.send("some_event", /* Optional payload */)