• 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:

    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 $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Partial Failed Tasks - Accept Error from API as Acceptable Result

refine

Member
Hi,

I'm currently using Pabbly to automate certain workflows in Hubspot. I have found Pabblyto be awesome when it comes to what you call "Partial Failed" tasks compared with Zapier. I love the fact that the Workflow continues and doesn't halt as some API's may return an Error result AND it's an acceptable response I can use the Pabble Router to take different actions depending on the outcome.

However, at this time I get an Email Notification everytime a Partial Error occurs EVEN if it's an acceptable outcome. In the future, wouldn't it be an option to configure a Task to accept ERROR without generating a Notification?

--

I understand that I could have used an extra Task to check before trying a Task to avoid an Error, however I think this use-case with an acceptable Error/Continue vs Error/Halt is useful in many cases.
 

Neeraj

Administrator
Staff member
Hi,

I'm currently using Pabbly to automate certain workflows in Hubspot. I have found Pabblyto be awesome when it comes to what you call "Partial Failed" tasks compared with Zapier. I love the fact that the Workflow continues and doesn't halt as some API's may return an Error result AND it's an acceptable response I can use the Pabble Router to take different actions depending on the outcome.

However, at this time I get an Email Notification everytime a Partial Error occurs EVEN if it's an acceptable outcome. In the future, wouldn't it be an option to configure a Task to accept ERROR without generating a Notification?

--

I understand that I could have used an extra Task to check before trying a Task to avoid an Error, however I think this use-case with an acceptable Error/Continue vs Error/Halt is useful in many cases.


We do have received similar feedback from multiple users about notifications.

We do have plans to offer an email notification management panel where you can control which messages you want to receive. Although it will take us a few months for that feature to be picked up and developed.

As of now, you will have to create a filter in your mailbox that can automatically archive the messages even before they hit your Inbox.

See screenshot:

1635912524180.png
 

refine

Member
Hi.

Thank you for replying.

In addition to a notification management panel, I suggest to add an option at Task level to Accept an ERROR from an API IF handled by the preceding task.

Another option would be similar to a Javascript try {} catch {} inside a workflow.

Thanks for listening...
 
Top