Timo Reimann
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
No worries 🙂
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
it's probably best for you to ask questions unrelated to the topic of this thread in the main channel.
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
the workflow
run method has a signature like this:
<Params> can be your custom type that you can also use on the caller site.21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
The empty ID problem is well-known, see multiple other mentions in this channel.
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
Great, thanks Luís.
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
Nice, that looks elegant.
I suppose that would cache succeeded steps at the per-
val level even if one of the many calls eventually failed?21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
The use case I have in mind is where you invoke an external API that returns a list, and then for each result or so you may need to invoke another API. Trying to think how to model that best and wondered if nesting would be helpful here or not.
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
Hmm yeah it guess it's not super useful when the outer and inner steps' fates are tied (which actually makes sense to be the case).
21 replies
CDCloudflare Developers
•Created by Timo Reimann on 10/28/2024 in #workflows-beta
Nested steps
Yes
21 replies