Lmmm, nice tutorial indeed
Lmy ADHD has issues processing the wall of text of the blog post, maybe with some pagination i could have tricked my brain to swallow the bullet
F
SWill we be able to set a workflow binding within a pages app sometime soon?
MCongratulations on the beta release! What are your thoughts on the future of Workflows? How do you plan to evolve it? Is it going to be a fully developed workflow system like Inngest or Trigger, or is it just the foundation?
DBeen waiting to try out Workflows for sooooo long! So glad it's finally here 
Was playing around with it a bit ... so cool and easy to use!
Was playing around with it a bit ... so cool and easy to use!
MGetting this link fixed.
MThis is just early days: it's a beta
DI might be able to even swap out Temporal for Cloudflare Workflows 
DI'm sure this has already been reported.. but seeing some weird flashing in terms to statuses?
DLike it flashes from Completed to Errored?
DLook's like it flashes when it's "Updating" ?
DDHmm interesting 
Feel like that would have been something someone would have noticed with months of testing
Feel like that would have been something someone would have noticed with months of testing DWill keep reporting the bugs as I see them 
DEven though my wall time says 5s 123ms (at the top).. I'm only getting charged the 2 wall times for when my function ran correct (26ms and 24ms respectively)? Shouldn't the "Wall Time" at the top right there say 26ms+24ms instead of 5s 123ms?
DCause wall time is what we're being charged correct?
DI'm not being charged for 5s 123ms of wall time here?
FAs far as I know Cloudflare never charges for wall time, only for CPU time
MCPU time only. Covered in the docs and the blog post:
Cloudflare Docs
Workflows pricing is identical to Workers Standard pricing and are billed on two dimensions:
The Cloudflare Blog
Cloudflare Workflows is now in open beta! Workflows allows you to build reliable, repeatable, long-lived multi-step applications that can automatically retry, persist state, and scale out. Read on to learn how Workflows works, how we built it on top of Durable Objects, and how you can deploy your first Workflows application.
DGotcha I thought Wall Time = CPU Time
DMakes more sense now thanks!
DAny technical downside to using custom IDs instead of the randomly generated ones?
EWhat are the memory constraints inside of a workflow? E.g download a big file, then do some processing in the next step
DWhat is the maximum size of a workflow request body?
SIf you mean the workflow instance payload ~1MiB
AA way around that would be to save it to r2/kv and then use in the next step?
SExactly, I had an idea to make an abstraction on top of workflows to save every step to R2 and lazily load steps as you actually need them, we don't do it by default because it kind of defeats the purpose of the free tier 
Cool side project for someone
as I don't have that much time to do it haahhaha
Cool side project for someone
as I don't have that much time to do it haahhahaDok
Dis there a simple way to let's say deploy hono into multiple workers?
Drn my build is quite small about 40kb but not sure how big things will get
Dbut well on paid plan there is bigger limit right?
Alooping at the code, you would not be able to emake an abstraction right. Because RPC is the only way to save it outside the step... So it would be creating something inside the step to 'save to r2' and 'get from r2'. It wouldn't be easier that just using the binding haha. Or am I missing something?
LIsn't this an oxymoron?
LSo you pay for CPU time, but you don't pay for Subrequests.
LSo if in my workflow I use fetch to get data from a website and that request takes 3s, I'm billed for that 3s of CPU time, so it's like I paid for the subrequest.
FWall time (e.g. awaiting a fetch request) is not CPU time.
LI guess that's a Cloudflare thing then, because your Worker would still be active while waiting
FYes, but in a sleeping state and not eating billable CPU cycles.
MDoes anyone know how invocation count works with workflows? Does a retry count as a new invocation? Are each step a seperate invocation?
Is a three step workflow that succeeds on the first try, three invocations (because there are three steps), or just a single invocation?
Is a three step workflow that succeeds on the first try, three invocations (because there are three steps), or just a single invocation?
FFrom how I read the documentation each workflow is a single invocation and steps do not count as another invocation.
FBut I'd love to hear this confirmed.
F(This should also be easily testable, just watch how the daily worker count changes on a free account)
MOh also, is there a way to limit concurrency of a specific workflow?
Let's say, downstream api is 100 req/min, I'd want to prioritize the oldest workflows and also limit concurrency. How would this look like with workflows?
Let's say, downstream api is 100 req/min, I'd want to prioritize the oldest workflows and also limit concurrency. How would this look like with workflows?
FI do not think you have control over that part.
FUnless you do some fancy self-organizing inside the workflow, maybe?
DAlready identified issue @Dmitry . Nevertheless, thank you for reporting!
