Troubleshooting the Agent
Use this table to diagnose common Agent issues, identify likely causes, and apply recommended fixes.
| Symptom | Likely cause | Recommended action |
|---|---|---|
| The Agent-generated link opens the wrong page. | The navigation target or page URL is incorrect. | Check the configured page URL and ask the Agent to update the navigation target. Test the result in preview mode. |
| The Agent response shows an error object or an unresolved error. | The generated query, component logic, or configuration is invalid. | Use Fix in chat, then review the Agent response and test the result again. |
| Fix in chat does not resolve the error. | The tenant may lack a required feature, field, configuration, or permission. | Inspect the MCP response and tenant configuration. Confirm access and Billing setup. |
| The query returns data, but the component is empty. | The Agent-generated binding or display logic is incorrect. | Ask the Agent to display the returned data and correct the field or variable reference. |
| The component shows realistic values that do not change. | The Agent created hardcoded values instead of dynamic bindings. | Inspect the query and binding. Ask the Agent to retrieve and bind the value to tenant data. |
| Preview crashes after an Agent change. | An Agent-generated interaction or Run code action is invalid or too complex. | Locate the lightning-bolt element, remove the interaction, and recreate it in smaller steps. |
| Undo is unavailable. | The page was reloaded and the in-session undo history was lost. | Restore a known-good published version. |
| The project is substantially broken. | Multiple Agent changes or a failed session left the project in an unrecoverable state. | Revert to a known-good published version and re-test it. |
| The Agent cannot reconcile the current changes. | The current chat context is too complex or contains conflicting instructions. | Start a new Agent chat using the earlier successful prompt as a starting point. |