Activepieces has been massively slow and degraded all day. Now, it’s not even working.
I’m able to replicate this in multiple browsers, multiple flows, etc.
Very frustrating as the status page does not show it and of course, I need it to be working.
Help! Attached an image of one of the error messages stating: An internal error occurred while fetching data, please contact support.
+1 unfortunately. AP is becoming very important for my agency. It’s really frustrating when I can’t get things done.
@Davide Totally agree. I really, really like them, and I’m ok with intermittent issues, but going multiple days with degraded performance is unacceptable in a platform like this.
@kishanprmr @Abdul @hazemadelkhalel
Any thoughts here? Thanks!
+1. Flows not responding, timing out. Causing major problems for myself and our clients.
@hanley Bummer, sorry to hear that. Same exact problem here. Big client deliverable supposed to be presented tomorrow…not looking good for me haha.
Would at least want AP to acknowledge and show it on the status page. The fact it hasn’t been acknowledged for a whole day is wild to me.
Respect to AP. Looks like they’re looking into it now. Thank you!!!
The team is currently taking look at that, they will publish full report once the outage is done
Same here, I thought it was me internet, even tried changing DNS, proxy etc., but the problem persisted.
I’m unable to save flows, test flow, do connections (using CODE piece) etc.
@mvpalves Lol, I thought it was me too!! Did all that stuff as well haha. Hopefully it’ll be fixed soon
@abuaboud Thank you so much!
The issue is now mitigated, we going to continue to observe the workers queue
Hi team, not sure if this is part of the same issue but I currently can’t maintain/build any flow as it keep hanging on Wait untill input is loaded. but there is no input…
I have been updating a very old flow in the Cloud holding a webhook version 0.2 and Google Sheet 0.8.4. When trying to replace the pieces I am receiving the internal error issue multiple times and now it keeps mentioning I need to wait for the input the load. The input never loads and keeps on spinning. Is there a way I can solve this? I currently can’t maintain/build any flow as this issue remains active over all flows…
Hi @here
We have been in constant fire fighting in past month to handle the scale and improve the reliability, I can confirm I see all jobs are being queued.
We got them down from 180k pending jobs, I see now it’s around 10k and all jobs should appear soon alongside publishing should works and these error should disappear.
We still have an issue that happen at first minute of each hour, where we get huge influx of data that get the app down for 30 seconds, we are collecting data.
We have tripled the size of infrastructure to handle all incoming traffic, we will post full details soon.
@Bram exact same thing happening to me. Wasn’t able to build/test/save any new flows unfortunately.
@abuaboud amazing! Congrats on the growth. Understand the growing pains for sure. Thank you for getting this worked on asap, appreciate it alot!
Since yesterday morning, we confirm our infrastructure scales significantly with the new worker.
We have one more minor issue where some webhook get 502 response at the first minute of every hour
