Sipke Schoorstra

I don't think it's a good idea to just close the response stream from within the `HttpEndpointMiddleware`. Even if it were, it's probably not a good idea or at the...

@zman2000 You’re right, I forgot that the timer activities have a small optimization where it skips scheduling altogether if the configured delay is zero or less.

Yes to the workflow name input validation, but I suggest we create a separate issue for that. A flag to control this sounds nice. There are probably other aspects as...

Officially, the workflow name should indeed be considered "technical" and follow standard programming naming conventions. So yes, the UI & backend should receive an update so that they validate the...

This is currently not supported, but a good feature to have.

Hi @Tenglingfeng The designer doesn't currently support time zones, but I'll keep your issue as a feature request. Thanks!

@minal87jadhav Can you please share an export of your workflow definition so we can take a look? As @dgumbo mentioned, it could be an issue with an expression. Of course,...

When hosting Elsa on multiple server instances, make sure to go through the steps outlined [here](https://elsa-workflows.github.io/elsa-core/docs/next/hosting/hosting-distributed-hosting). Each workflow definition will be stored in a local cache on the server. To...

> I would say things work correctly 95% of the time, that's why we are in trouble. I'm wondering how I could be checking if these signals are fired and...

@vargaendre > How can we make sure that our multinode setup is correct? We followed the article you mentioned, instances start, we don't see errors, still it would be great...