"This record couldn't be saved because it failed to trigger a flow" when one of the field in the Object contains many characters
Last updated 2016-12-08 ·Reference W-2774871 ·Reported By 47 users
Running a Process will return an error on certain records. It doesn't depend on the object (i.e. it can happen in Accounts, Cases...) but rather on the size of the text that is being passed on one of the fields for that record.
1. Create a process with a scheduled action on Account
2. Create an account and fill the description in until no more characters are allowed
3. Trigger the process from step #1
None at the moment.
The only workaround would be to shorten the information on the field that is causing the issue. Unfortunately there's not a hard limit where this is occurring as it depends on the size of the entire entity and not just a single field (i.e. other long fields may cause the error to appear with shorter descriptions).
It seems that a safe figure would be under 18k characters but please note that, based on other circumstances, you may need to adjust it more.
Reported By (47)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.