Does anyone else seeing some steps get stuck in running for quite some time?
Does anyone else seeing some steps get stuck in running for quite some time?
/link so that we can have a look?step.waitForEvent? Not sure if it's happening in production, but it makes going through logs locally pretty messy. 



Attempt failed due to internal workflows error error?waitUntil supported / recommended in Workflows? table property anywhere, and i've verified the types are correct. it works fine locally—any ideas on how to root cause this?isolatedStorage flag to be set to false (otherwise, vitest doesn't recognize the entrypoint?). However, since setting isolatedStorage to false , we see a different error related to queues..create() with the whole error being just internal error
500s intermittently with 10001: workflows.api.error.internal_serverinternal error on workflow binding .create() since. However, falling back to the HTTP workflow POST .../{workflow_name}/instances api (with the exact same workflow id + params, it succeeds
waitUntil code? waitUntil, because it garbage collects the state and tears down the execution environment after the Workflow instance is registered but BEFORE the workflow is actually run. The sleep prevents the premature shutdown of the Worker execution context. run method without wrapping it inside a step.do. My examples are zod validation of params or something like const ai = new GoogleGenAI().. I theory I don't want to persist those, I'm fine if they run again on a new try. So would it be best to put them in the global run scope?// Worker
ctx.waitUntil(
nonBlockingFunc({ ... })
);
async nonBlockingFunc() {
const workflowInstance = await env.MY_WORKFLOW.create();
// await new Promise((resolve) => setTimeout(resolve, 2000)); // sleep fixes???
return workflowInstance.id;
}/link{
payload: {
result: ... // my result data
},
type: 'sub-request-complete',
timestamp: 2025-06-05T17:01:09.650Z
}Attempt failed due to internal workflows errorConverting circular structure to JSON
--> starting at object with constructor 'PgTable'
| property 'id' -> object with constructor 'PgUUID'
--- property 'table' closes the circletableisolatedStorageisolatedStorageQueuesError [ERR_MULTIPLE_CONSUMERS]: Multiple consumers defined for queue "<queue-name>"50010001workflows.api.error.internal_server