No Observability To What is Failed in creating workflow
Hey, I'm not sure if workflows is the right destination, but I feel this could be a more general issue.
I've encounter in a couple of times, that when I batch create (<4500) workflow instances but at 400 or something, I experienced significant wall time for the request to complete as queued build up, this contradict to what cloudflare mentioned in the docs of 4500 concurrent workflow instances. But also, when I have several hunderd of instances being queued, I got a ton of internal error that I have no clue of what's going on, and the queued instances often take a long time for them to get running. Sometimes, when looking at the log, I got no visibility as to what is preventing me from spawning more workflows.
So, is observability panel the right way to access those information because I've got no visibility as to what's going on with my request.
{
"source": {
"message": "internal error",
"exception": {
"stack": " at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async handleScheduledEvent (index.js:77373:18)\n at async Object.scheduled (index.js:81123:5)",
"name": "Error",
"message": "internal error",
"timestamp": 1749823912326
},
"$cloudflare": {
"$metadata": {
"id": "01JXMT3YC6AXV8VV4G079ZTV9E",
"type": "cf-worker",
"error": "internal error"
}
}
},
"requestId": "3YWPOIJ1EJVZRW9Z"
},
"$metadata": {
"id": "01JXMT3YC6AXV8VV4G079ZTV9E",
"requestId": "3YWPOIJ1EJVZRW9Z",
"trigger": "* 13-21 * * mon-fri",
"service": "inmoney-api",
"level": "error",
"error": "internal error",
"message": "internal error",
"account": "1a846a3aa6bfc55b1f8ca8bee4c4bdce",
"type": "cf-worker",
"fingerprint": "1ef5291ce4c67da75b431843ca5a4c27",
"origin": "cron"
},
"links": []
}
I've encounter in a couple of times, that when I batch create (<4500) workflow instances but at 400 or something, I experienced significant wall time for the request to complete as queued build up, this contradict to what cloudflare mentioned in the docs of 4500 concurrent workflow instances. But also, when I have several hunderd of instances being queued, I got a ton of internal error that I have no clue of what's going on, and the queued instances often take a long time for them to get running. Sometimes, when looking at the log, I got no visibility as to what is preventing me from spawning more workflows.
So, is observability panel the right way to access those information because I've got no visibility as to what's going on with my request.
{
"source": {
"message": "internal error",
"exception": {
"stack": " at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async handleScheduledEvent (index.js:77373:18)\n at async Object.scheduled (index.js:81123:5)",
"name": "Error",
"message": "internal error",
"timestamp": 1749823912326
},
"$cloudflare": {
"$metadata": {
"id": "01JXMT3YC6AXV8VV4G079ZTV9E",
"type": "cf-worker",
"error": "internal error"
}
}
},
"requestId": "3YWPOIJ1EJVZRW9Z"
},
"$metadata": {
"id": "01JXMT3YC6AXV8VV4G079ZTV9E",
"requestId": "3YWPOIJ1EJVZRW9Z",
"trigger": "* 13-21 * * mon-fri",
"service": "inmoney-api",
"level": "error",
"error": "internal error",
"message": "internal error",
"account": "1a846a3aa6bfc55b1f8ca8bee4c4bdce",
"type": "cf-worker",
"fingerprint": "1ef5291ce4c67da75b431843ca5a4c27",
"origin": "cron"
},
"links": []
}
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
87,353Members
Resources
Was this page helpful?
