Hi,
Yes I found a workaround.
Initially I had problems because I was using SQLite and I had lock problems
that led to ugly SQLAlchemy errors.
After changing to Postgres SQL I got rid of lock errors but I had same
issue.
So I tried to create a simple script (my workflow has 14 processes)
from co
Hi,
We had this behavior when we used the default SQLite.
Since we switched on MySQL, it fixed this :P
Maybe a clue for you ?
Gildas
Le 18/06/2014 18:33, Carlos del Ojo a écrit :
Hi All,
I am using the API (posting to 'http://localhost:8080/api/workflows' )
and running 8 workflows in a row.
Hey Carlos,
Have you made any progress on this, I have never heard of this
behavior but at the same time it does not surprise tremendously
either. How large is the workflow? If large - you will almost
certainly want to make sure you are using a Postgres database server
instead of sqlite. Likewis
