Is there a way to have a monorepo of several workflows in one repository ?
Is there a way to have a monorepo of several workflows in one repository ?
Worker "workflows:demg-test-workflow"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "TestWorkflow", but "core:user:" has no such named entrypoint. occurred. I've created a minimal repo to recreate and added the full log message in this issue FYI. https://github.com/micksabox/remix-cloudflare-workflows/issues/1
Worker "workflows:interaction"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "InteractionWorkflow", but "core:user:" has no such named entrypoint.The destination execution context for this RPC was canceled while the call was still running.wrangler workflows instances describe there is no equivalent for local right?
await step.sleep('wait on something', '1 second') but here it says the wall time for this step is 254ms .. any idea why it's lower than what the wall time should be?
wait on something (Sleep)workflows = [
{name = "first-workflow", class_name = "FirstWorkflow", binding = "WORKFLOW_ONE"},
{name = "second-workflow", class_name = "SecondWorkflow", binding = "WORKFLOW_TWO"}
][wrangler:inf] GET / 500 Internal Server Error (48ms)
[wrangler:inf] GET /favicon.ico 404 Not Found (2ms)
id null
creating new instance RpcStub {}
[wrangler:err] TypeError: Cannot destructure property 'id' of 'undefined' as it is undefined.
at async Object.fetch (file:///Users/srb/projects/elater-cf-workflow/workflows-starter/src/index.ts:84:18)
at async jsonError (file:///Users/srb/projects/elater-cf-workflow/workflows-starter/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
at async drainBody (file:///Users/srb/projects/elater-cf-workflow/workflows-starter/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)Worker "workflows:demg-test-workflow"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "TestWorkflow", but "core:user:" has no such named entrypoint.Worker "workflows:interaction"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "InteractionWorkflow", but "core:user:" has no such named entrypoint.