Hey Sean / Team @Left Hook!

...the user-facing error message is getting truncated when sending back a long string…

Is there a way to return an object to the Zapier editor so that the user can drill down further instead of getting a truncated message?

When it comes to showing errors in the Zap Editor, there isn’t currently a way to return an “object” that would present users with a UI that would offer a way to navigate/drill-down into that “object”. 

Or are we just limited to a character limit for the string and that’s that?

If so, what’s the character limit?

I created an action that returns an error message (via z.error.Errors) that has 1,000 words in the error message. The first 247 characters are initially displayed but a “Show More” link displays all 1,000 words after it is clicked on. This provides the ability to display a lot more information in the Zap Editor than would probably be considered user-friendly for an error message:

The Zap History page takes the same approach. However, due to UI constraints, it shows much less of the error message when the “Show Details” link is clicked on:

In cases where there’s a lot of data for the user to take action on

Please could you post some more details (screenshot / mockups etc) that show an example of this kind of error and how and where you’d like users to be able to view that information? 

That will help us to make further suggestions on what’s currently possible but also to create a new feature request for any changes you’d like to see