apremierdj
Member
I have a workflow "DJ Chris Abell Text Found on Page" that randomly disables multiple times a day. Can someone please explain why and how to stop from disabling?
-
Instructions to Ask a Question
Click on the "Ask a Question" button and select the application for which you would like to ask questions.
We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.
The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!
🚀🚀Exclusive Discount Offer
Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) - View offer
🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer
-
Workflow keeps auto disabling
- Thread starter apremierdj
- Start date
Hello @apremierdj,
Please enable the disabled workflow and try saving any paid action step in your workflow—this should prevent the workflow from being disabled. Kindly test it and let us know if everything works fine.
Please enable the disabled workflow and try saving any paid action step in your workflow—this should prevent the workflow from being disabled. Kindly test it and let us know if everything works fine.
apremierdj
Member
Still disabling after trying your recommendation
Dear @apremierdj,
Upon reviewing the workflow history, we observed that the workflow is functioning; however, the "API by Pabbly" action is failing due to the API not responding within the 25-second timeframe.
Additionally, we confirm that the workflow has not been disabled after March 3. Please refer to the attached images for further details.
Let us know if you need any assistance.
Upon reviewing the workflow history, we observed that the workflow is functioning; however, the "API by Pabbly" action is failing due to the API not responding within the 25-second timeframe.
Additionally, we confirm that the workflow has not been disabled after March 3. Please refer to the attached images for further details.
Let us know if you need any assistance.
apremierdj
Member
Can you check again as the workflow is disabled again and I have not done anything.
My other workflows in this folder also return errors but do not auto disable because the API returns error.
There must be another reason
My other workflows in this folder also return errors but do not auto disable because the API returns error.
There must be another reason
jmjmjm
Member
So here you are saying that the issue is not getting a response within a particular timeframe? I suspect this could also be my issue too.. Would that mean it wouldn't show up in the workflow history? That's confusing me since my workflows are just disabling themselves without any auditable trail that suggests that were ever attempted - they just turn off. But the timing clearly is linked with attempted runs (from where i've specifically forced a run via the prior workflow).
Our team is actively working on fixing this issue. Please allow us some time, and we will get back to you with an update soon.
jmjmjm
Member
Thanks - can I check what you've diagnosed it as? It's not impossible that API calls could take 30 seconds plus to get an answer, but the fact it's saying about the workflow being disabled for having used too many free tasks is what makes me think it's a technical but within the wider platform (having found threads like this one with same issue as my own original thread). Thanks
It is not related to API calls taking 30 seconds or the workflow having only free tasks.
Yes, it is a system-wide technical issue that our team is working on.
Similar threads
