its not the case. why would you think that?
its not the case. why would you think that?
cause of the error is not set. Is that expected? Makes it hard to communicate data from the failed step to the recovery flowstep.waitForEvent not count towards the total step count per workflow, similar to step.sleepexponential is it 2?POST https://dash.cloudflare.com/api/v4/accounts/e97e3fed722428f4d726062eae9aa766/workflows/workflow-orchestrator-staging/instancesstep.do but it is nowhere to be found from the logs tab of the worker. I also cannot find anything on the Instance ID of the workflow invocation.
await this.env.WF_FILING_INGEST.createBatch(batchParams); and call their status() function?
Maximum Workflow instance creation rate Limitcall to createBatch is treated the same as a call to create (for a single instance) and allows you to work within the instance creation limit.
createBatch , if you were to create 100 instances per batch (the maximum), that you could create 10,000 instances (100 per batch * 100 calls) per 10 seconds?causestep.waitForEventstep.sleepexponentialPOST https://dash.cloudflare.com/api/v4/accounts/e97e3fed722428f4d726062eae9aa766/workflows/workflow-orchestrator-staging/instancesawait this.env.WF_FILING_INGEST.createBatch(batchParams);status()Maximum Workflow instance creation ratecreateBatch