-
Instructions to Ask a Question
For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.
We offer seven comprehensive applications designed to help you efficiently manage and grow your business:
- Pabbly Connect
- Pabbly Subscription Billing
- Pabbly Email Marketing
- Pabbly Form Builder
- Pabbly Email Verification
- Pabbly Hook
- Pabbly Chatflow
Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.
🚀 Exclusive Lifetime Offers 🚀
We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:
- 🔥 Pabbly Connect — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Subscription Billing — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Chatflow — Lifetime Access for $249 — View Offer
Make a one-time investment and enjoy the advantages of robust business management tools for years to come.
-
Text Formatter by Pabbly timed out
- Thread starter dataforge
- Start date
Fagun Shah
Well-known member
You can just replace that Text formatter action with the same action name which does not have deprecated at the end.
Fagun Shah
Well-known member
What does deprecated sign means?
While using Pabbly Connect, you might see the deprecated sign as shown below - Deprecated means a better version of the module has been launched, and we recommend using the new version. Deprecated actions, triggers or app may be usable, but it is considered obsolete and should be avoided...
forum.pabbly.com
Ivan Arnaudov
Member
Two workflows with multiple text formatter operations failed me as well today. This is the first time I see that the text formatter has been deprecated.
Not cool, dammit. We should be informed when a workflow component gets deprecated. It is not realistic for the user to recheck their workflows by hand every month to see which function has been changed.
Pabbly Connect: we need better communication from you.
Not cool, dammit. We should be informed when a workflow component gets deprecated. It is not realistic for the user to recheck their workflows by hand every month to see which function has been changed.
Pabbly Connect: we need better communication from you.
Fagun Shah
Well-known member
Ivan Arnaudov
Member
Yeah. Well. No.
Facebook is not good for this kind of information. I have all sorts of notifications enabled and yet I did not see this message.
But even if I did, this is not the way to handle important updates. There should be one single stream of official communication where (1) all sorts of important changes are announced in advance and (2) people are push-notified to update.
Specifically, I remember when the Number formatter update was announced. But do I have to remember if I have used every component that is getting deprecated one day? Do I need to remember where I have used it?
This kind of announcement sucks, it is worded as if it is the users' fault. Quite a bit ironic for a company that offers automation, not to be able to automate the process of informing its users that a change is coming, or has been enacted, and that they should plan ahead and switch at an opportune time.
Not to mention that the change itself required me literally to copy/paste some text strings from one block of fields to another. The format of the service did not change, why isn't there a single-click update function to port these values into their new placeholders? Why is even updating required and why aren't deprecations migrated silently?
This is the first time I am getting really pissed with the service, and that is because this is something very simple to improve. I did not have to rush back to my PC after work hours to update a time critical parser. It was something that could have been handled way better.
Facebook is not good for this kind of information. I have all sorts of notifications enabled and yet I did not see this message.
But even if I did, this is not the way to handle important updates. There should be one single stream of official communication where (1) all sorts of important changes are announced in advance and (2) people are push-notified to update.
Specifically, I remember when the Number formatter update was announced. But do I have to remember if I have used every component that is getting deprecated one day? Do I need to remember where I have used it?
This kind of announcement sucks, it is worded as if it is the users' fault. Quite a bit ironic for a company that offers automation, not to be able to automate the process of informing its users that a change is coming, or has been enacted, and that they should plan ahead and switch at an opportune time.
Not to mention that the change itself required me literally to copy/paste some text strings from one block of fields to another. The format of the service did not change, why isn't there a single-click update function to port these values into their new placeholders? Why is even updating required and why aren't deprecations migrated silently?
This is the first time I am getting really pissed with the service, and that is because this is something very simple to improve. I did not have to rush back to my PC after work hours to update a time critical parser. It was something that could have been handled way better.
Ivan Arnaudov
Member
P
PabblyMember3
Guest
Hey @Ivan Arnaudov ,
Thanks for your feedback,
We will discuss with the team internally on your suggestions and work on it.
Also, we've checked the deprecated actions of all formatters and now its working fine. Still, you are requested to use the updated actions of formatters in your workflows instead of using the deprecated ones.
Thanks for your feedback,
We will discuss with the team internally on your suggestions and work on it.
Also, we've checked the deprecated actions of all formatters and now its working fine. Still, you are requested to use the updated actions of formatters in your workflows instead of using the deprecated ones.
Similar threads
- Locked
- Locked
