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

text formatter Internal server error

dbs00

Member
Your Workflow URL
https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTY4MDYzNjA0MzY1MjZiNTUzMTUxMzYi_pc
Your Task History ID
IjU3NjUwNTZhMDYzNjA0MzQ1MjY0NTUzMDUxMzA1MTY3NTQzNzBmMzgi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
hey
check these
How can I prevent this error ? I noticed it a lot lately

check the history, it has multiple different tasks with that error
 

Preeti Paryani

Well-known member
Staff member
Hello @dbs00,

The issue occurred because the Code (Pabbly) step (Step 5) was returning a syntax error. Since the Text Formatter step has data mapped from Step 5, it was unable to find the specific mapped key, which caused the error to appear.

1760515582062.png
 

Preeti Paryani

Well-known member
Staff member
Hello @dbs00,

Upon checking the task history, it appears there was an internal error. Based on the data available, it seems the issue occurred because the JSON structure was breaking—most likely due to double quotes present within the mapped text.

Since the step has now been deleted, I’m unable to identify the exact element causing the break, but the error was likely triggered by those double quotes in the mapped data.
 
Top