It seems like there should be a standard for user error messages -- those generally beyond the user's control.

This is what should generally be supplied:

1. A clear error message statement, including the system or subsystem that threw the error.
2. Brief explanation of what the cause could have been the problem, to put the user at ease.
3. What recovery is available? Is the system unavailable, or it fixable for that user?
4. Error Details for capture (Including timestamp, SessionID, etc)

The authentication failure messages generally follow this pattern ("Connection Failed. Try again"), but not exactly -- leaving us customers to fill in the gaps here.

We are unable to customize those messages from the engine, unfortunately.

Can that be considered?

(or can we anticipate Pega getting errors cleaned up following some standard?)