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

Field(s) image character length exceeded error

Jorge

Member
Your Task History ID
IjU3NjEwNTZhMDYzNzA0M2Q1MjY0NTUzMDUxMzA1MTY0NTQzNCI_3D_pc
Since yesterday I'm receving this kind of messages in some of my flows, I have this flows working since 3 months ago and this error start appearing since yesterday in 4 workflow. Im using Ultramsg in all this flows

"status": "error",
"message": "Field(s) image character length exceeded the allowed max value. Learn more: https://forum.pabbly.com/threads/maximum-character-length.10600/"

Can you help me please? I don't know what it means.

Thanks for your help.
 

Himesh

Active member
Hello @Jorge , Let me explain you this scenario. E.g. You have one field called image and suppose it's character length value is 1000 (Image name or Image Url should be within 1000 characters) and you are getting image url or Image name more than 1000 characters from previous step(Action or trigger) in that case you'll get this error.
 

Jorge

Member
oh! I see...I thought it was related to the lenght of my message text, because I erase some word in the message and it work correctly...This is new? because I had some scenarios working correctly and this error is something that start to pop up this week. Thanks!
 
Top