workers-and-pages-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
🤖turnstile
radar
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
vite-plugin
pipelines-beta
containers-beta
Hi, is there a way to get the statuses
Are there any best practices for
I see one of the workflows examples
Now I'm running into this as well `(
(workflow.not_found) Provided Workflow does not exist
in production.
Anyone on the Cloudflare team know what could be happening? Seems a few other people have run into this....workflow not found debugging 05/05

😬 , i am running bullmq for now buts
I am not sure what has happened with
10001
as earlier.
Over 3000 workflows failed yesterday with the exact same error This instance experienced an internal error which prevented it from running. If this is persistent, please contact support: https://cfl.re/3WgEyrH
...I might have identified a bug related to
I'm experiencing some cases where new
queued
status foreverWorkflow run in "waiting" state
I haven't had any issues so far but also
So after further investigation, it turns
npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter"
...I'm running into a somewhat frustrating
cloudflare
npm package …Suddenly whenever my worker invokes my
could you get me your account id please
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!...