Forum archive
processmaker completed tasks staying as draft(solved)
HI all my first post here. I downloaded and installed processmaker virtual appliance , which was great except after defining a process the tasks would not progress to the next person.
It took me several hours of tracing down rabbit holes and dead ends, re-installs etc, until I found a comment in one response of a thread that solved my problem. I'm just sharing my solution in case someone else has this problem or someone wants to investigate or not.
The solution was a missing/not started background task once I started it everything works as it should.
to start the process I execute 2 commands
- cd /var/www/processmaker
- php processmaker artisan queue:work --workspace=workflow
I dont know if thats the best way to do it , or if should be done some other way(I added this to a cron reboot)
Replies (4)
Hmm, I wonder if it's because we don't ship a cron job?
Reply 1missing content
Reply 2looks like the origina content is blank so I'll repeat my comment here
to get the appliance to work I did the following
cd /var/www/processmaker
php processmaker artisan queue:work --workspace=workflow
Please configure the cron job as noted in the issue
Reply 3We haven't yet resolved this issue. We hope to have an updated appliance soon. In the meantime, I suggest adding the cron job as noted in the issue.
Issue is still happening with initial turnkeylinux install..
Reply 4Your fix with the two commands worked
cd /var/www/processmaker php processmaker artisan queue:work --workspace=workflow
Can you explain why that fixed it ? Is workspace not defined in the artisan queue? I assume i don't have to do this at every boot but theres only one way to find out ;)
Hi there. I have just had a look at the build code and it appears that we aren't shipping the appliance with a cron job. I wonder if that's why this didn't happen automatically? I suspect so... ('queue' jobs are generally run by cron).
Regardless, it should have a cron job. So I've opened a new issue for that. I have posted a workaround there to create the suggested cron job (taken from Processmaker docs). I suggest you apply that and hopefully that should resolve this in future (without requiring you to manually run commands).