Sipke Schoorstra

Thanks for the input @bbenameur , we can use your test case to verify the feature proposed here 👍🏻

Hi @hsnsalhi , Indeed, unfortunately we will not be able to include this capability on time for the 3.1 release which is slated for this month. It will be picked...

Hi @rosca-sabina , Unfortunately this feature has been pushed down again due to other priorities. It's unknown at this point when this can be picked up.

It depends on the situation. Features driven by customer requests are typically implemented quickly, while other features are developed more organically, making them harder to plan for.

Hi @Ramedlaw-knil, >This capability seems essential for building resilient applications, especially in production environments where workflow interruptions due to crashes must be reliably recoverable. Without this functionality, it would be...

We haven’t fully committed to the Graceful Shutdown feature yet, but odds are that development will start somewhere within the next 4 to 8 weeks. From that point, it will...

Thanks for the feedback and questions! I’m new to governance but inspired by [CIP1694](https://cips.cardano.org/cip/CIP-1694). I aim for a governance model that’s fair, transparent, and scalable, with this initial version being...

Hello @dwevedivaibhav, Thank you for bringing this issue to our attention. I really wish I could offer a specific timeline for addressing it, but currently, my schedule is quite packed...

Makes sense. Probably, we also need to consider that at some point a server will go down, e.g. when hosting in a Kubernetes cluster. If a workflow instance is still...

Thanks for reporting this! The error you're seeing: ``` Incorrect syntax near 'OFFSET'. Invalid usage of the option NEXT in the FETCH statement. ``` ...typically happens when the database is...