workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
âš¡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
vite-plugin
workflow create batch issues
Creating a workflow that is iterating
next_cursor
so that you know the next page to go and fetch. My question:
Can I capture the next_cursor in a let like below to reference in each subsequent step?
```ts
let next_cursor;...Right, we should have expected retry
Running
state. When I queried for the events for this instanceId via the GraphQL analytics API - there was only 1 ATTEMPT_START for that ID, I do not see that any retries were executed.
Even after I terminated the instance, while the workflow run changed the status to Terminated
, the step status still says Running
. See screenshot. Perhaps I've misconfigured something?
Thank you for your help!...
If I try and use cross-script calls like
I have workflow working locally and I
c.env.COVE_WORKFLOW_VIDEO.create({
I think it is saying that the actual workflow is not bound.
below is the hono api call that triggers it...It might be naive question but i am
Hey, i'm noticing a lot of errors with
A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset
is it just me or is anyone else having the same issue? 🤔...Hi all, just started using workflows.
Gotcha - ok, thank you! I'll do some
fetch()
.can someone confirms AsyncLocalStorage
Hey!
Workers RPC — Lifecycle · Cloudflare Wor...
An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it.
I see that step.do
expects to return Rpc.Serializable<unknown>
, so I did a little bit of reading about the RPC lifecycle here and found that in the context of Worker Service Bindings, you should either use the experimental using
syntax, or explicitly call object[Symbol.dispose]()
.
...Hi folks - having some trouble with
const wf = await MY_WORKFLOW.get(id)
and then await wf.status()
should return errors, but they are always empty....is `npx wrangler types` supposed to work
npx wrangler types
supposed to work for workflows?
wrangler.toml: services = [{ binding = "WORKFLOW_PROCESS_TRANSACTIONS", service = "money" }]
wrangler version: wrangler 3.107.3
generated interface, WORKFLOW_PROCESS_TRANSACTIONS should be Workflow?
```...Workflow limits
Hi all. Is it possible to pause/resume
Error handling seems quite complex. I
I'm getting this error with the