How to use the Error Message Generator.
An error message should state what happened and the available recovery action. Do not expose sensitive internals or blame the user.
Make the workflow fit your task.
State the specific problem and the available recovery action using the user's terms. Preserve enough detail to locate the issue without exposing sensitive internals, and distinguish a correctable input problem from a system failure.
- What you provide
- Actual error condition and recovery options.
- What you get
- Actionable error copy without blaming the user.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
CSV import fails because the required SKU column is missing.
Completed example
This file is missing the SKU column. Add it to the header row and try the import again.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should an error message explain every technical cause?
Give the information needed to recover. Detailed diagnostics can belong in an appropriate support or logging channel rather than the visible message.
Why does the message say try again when nothing can change?
Provide the actual corrective action or a truthful next step. Repeating an impossible action adds frustration without resolving the failure.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑