Hi All,
Whenever there is an error in our Confluence Cloud app’s Forge resolver and we want to provide custom details (object with validation error details as payload, a flag to indicate whether to retry the request, etc.), we are limited by Forge to sending an error message as string which is automatically prefixed with There was an error invoking the function - . So far, we at least had a way to work around this by sending the error object as stringified JSON, but Forge recently started truncating these error messages, breaking this workaround. I found no trace of this change in the official changelog, but I may have missed something. Error messages are pretty much useless in their current form.
Can we either have this limit on the length of error messages removed, or ideally, get a way to return a custom payload along with the error?
This is not a new problem, see this thread that got completely ignored by Atlassian Staff: Error handling in Custom UI resolver