Nyamath Shaik

@cdavernas Thanks for letting me know! 😊 Could you please take a look at the issue [#1096](https://github.com/serverlessworkflow/specification/issues/1096) and let me know if the proposal looks good to move forward? Happy...

@JBBianchi @cdavernas No, we can't simply use `EXIT` as a replacement for a dedicated break task. Here's why: **Different scope:** - `EXIT` is a transition type that exits the entire...

@cdavernas @JBBianchi @ricardozanini I was trying to check if this works on `synapse` looks like it doesn't I have tried both below and it doesn't break the loop. - for...

Hi @cdavernas @JBBianchi, One issue I’ve observed with the current `then: exit` approach is that it exits the current `do` scope only, not the entire `for` loop. This becomes a...

@cdavernas Yeah, I understand that its a bug on synapse where then:exit is currently behaving like a `continue` instead of a `break` However, if even we fix the bug, `then:exit`...

However, It appears that the current `for` task can be utilized as a loop, allowing a For task to operate as a traditional while loop in Serverless Workflow. By setting...

May I know if `for` is mandatory or can we get it of ``` for: in: ${ [] } ``` According to typescript SDK it's optional, but its no-where that's...

@cdavernas Thank you for the feedback. I was considering something along the lines of the following, but I am still open to suggestions. Please review it and let me know...

@cdavernas Thanks a lot for the feedback and kind words! 🙌 Really appreciate you taking the time to review the proposal. Totally hear you on the concerns around the `while`...

or how about just simply renaming the initial proposal to below : ``` do: - fetchPaginatedData: condition: .hasNextPage == true isDoWhile: true # Enables do-while behavior limit: 100 do: -...