I have a simple flow that is scheduled to run every day at 6am which outputs a telegram message after collecting data from various API’s. I had it working flawlessly for a few weeks and then all of a sudden it stopped running. Tried a few things, eventually the tests were succeeding, it ran for 3 days then stopped. Then I changed the value of “run on weekends” back to “dynamic” and then it started working again. Worked for 2 days then stopped.
It’s infuriating to me that you have to pay for enterprise for something as critical as “issues”. I’m so close to moving to n8n because this platform is BS.
Definitely don’t recommend Active Pieces for anyone who has anything even remotely critical they’re needing to run. This is a toy app and the devs seem to be using the users for QA and testing. I’m sorry it’s just so frustrating that I feel like I need to vent.
Anyway, if anyone has any suggestions for me, I’ll give it one last chance before I pack it in and start re-building on another platform.
Instance is selfhosted:
Hi @bluestreak
If you are self hosting, make sure you use the setup with “Redis” in docker compose, and then you can view all jobs in bull board.
Let me know which mode are you using, the one with Redis or with Memory.
@abuaboud appreciate the response, I’m really only posting this to help people reference these issues in the future.
To answer your question - yes, I am using Redis with my Activepieces instance. I do have access to the “Jobs” and “Runs” pages, however, they are COMPLETELY useless.
My job is enabled and when I “Test Flow” everything works great. But the job just has absolutely no consistency for when it actually decides to run or not. So I’ll fiddle with it for a bit and then the next few days it executes no problem. Then out of the blue it will just not run. So I go back and there is no way for me to see if it failed or if there’s something wrong or check logs. There’s no record of it in “Runs” so obviously it didn’t execute at all. There’s no way to access the “Issues” page so I’m not even sure if that would help me.
For anyone reading this just starting out with Activepieces, just be warned, this is not production ready software. Do not attempt to run critical automations using this tool. It is not stable, or consistent. There is little to no way to troubleshoot besides changing things at random and hoping for the best.
This issue was 2 months ago and has still not been resolved, no support, no bug fixes, no way of troubleshooting. It just works in testing and then seemingly never runs. Honestly, I’d be happy to be proven stupid and shown what I’m doing wrong, but I don’t think it’s something in my control.
Good luck to you all, I’m off to another platform.
