Hi Luis - are you still working on flowcesinha (or any word on when any of these things will get int
Hi Luis - are you still working on flowcesinha (or any word on when any of these things will get integrated into Workflows)?
<MY_WORKER>/production/settings#bindings then workflows are not shown. I was going to add them manually as a service, but am I going to have to do this for every deployment?events and i have been inserted already, so that way on retry you would just check the kv for where to start. - depending on db you might also want to do all the inserts as a batch after events.length has been processed, which would reduce the number of kv writes to track i.await env.MY_WORKFLOW.createBatch(listOfInstances); it's returning [{"fetcher":{}}] instead of WorkflowInstances?errored is both a terminal and transient state. There should be a separate state signalling the workflow has exhausted all retries.
<MY_WORKER>/production/settings#bindingseventsiievents.lengthawait env.MY_WORKFLOW.createBatch(listOfInstances);[{"fetcher":{}}]erroredDescribing latest instance:
Workflow Name: workflows-starter
Instance Id: c369baf1-8d53-4f35-be6b-47c037ff0cb0
Version Id: e2306101-587c-46a1-9451-14a9bef15921
Status: ❌ Errored
Trigger: 🌎 API
Queued: 6/1/2025, 12:40:50 PM
Success: ❌ No
Start: 6/1/2025, 12:40:50 PM
End: 6/1/2025, 12:40:52 PM
Duration: 2 seconds
Error: Error: internal error; reference = la5trq1a8b4ie9ka6vclinv6
Steps: