Sipke Schoorstra

I can't seem to reproduce this with any of the existing workflow providers. Perhaps there's something off wit your custom provider. Would you be able to share it (or a...

Hi @mlditga , thank you for your PR! As it turns out, this issue doesn't exist with EF Core, but with MongoDB and YesSQL providers. Would you be willing to...

Hi @mlditga Just updating the MongoDB provider is enough, you don't have to do it also for YesSQL. Doing it in a transaction would be nice, but not a hard...

Thanks for letting us know @mlditga. We'll close this PR.

So the application just gets stuck, no exceptions or anything? Can you reproduce this on your local machine (using a copy of the DB)?

Try this: ```liquid {% assign my_variable = Variables.Test %} {% if my_variable==1 %} new Approval Proccess {% else %} new Aprroval process for Client {% endif %} ``` Notice that...

The "fire and forget" term is misleading in this context. What the **Run Workflow** activity actually does is execute a workflow and *wait for it to either complete or get...

Originally I wanted to support the ability to read input properties, but that would require evaluating input expressions before evaluating the JS expression. We would have to do this for...

Thanks for raising awareness of this issue!

I’ve been building Elsa solutions on DevOps for a few years snow, never had an issue with path names being too long.