How to use the Stack Trace Explainer.
A stack trace shows the path to a failure, not necessarily its original cause. Find the relevant application frame and inspect the data reaching it.
Make the workflow fit your task.
Locate the relevant application frame and inspect the values and calls leading to it. Explain what failed at that point, then trace backward to the missing condition without assuming the last line contains the original cause.
- What you provide
- Error trace and application context.
- What you get
- Failure path and diagnostic next steps.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
TypeError occurs when code reads user.name and user is undefined.
Completed example
Check where user should be assigned and why it is absent; choose appropriate missing-user handling rather than hiding every error.
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 every stack-trace frame be edited to fix the error?
Find the responsible application behavior first. Framework and library frames often show propagation rather than the defect's source.
Why does optional chaining remove the exception but leave the feature broken?
It may hide a required value's absence. Decide whether missing data is valid or indicates an earlier failure that needs correction.
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 ↑