Action Errors showing up in server logs

[bryan-robitaille]

Part of the amazing workings of Server Actions is that the server error is transmitted back to the client browser where it can be handled or caught by the Error Boundary.

The issue is that even through the error is handled client side the unhandled server error is printed to server console which is caught by our system monitoring and raises an alarm in slack.

Server	Browser

We should ensure that when and action is expected to throw an error, for example deleting a form that has existing responses, that the errro is handled server side and transmitted in a safe fashion to the client to activate the corresponding toasts.

Acceptance Criteria:

• All Server Actions are reviewed and updated to ensure that all actions that throw errors are transitioned to instead send the error message through a property back to the client.

[srtalbot]

Out of scope: client-side handling, app team will be focusing on it.