Troubleshoot ADT

Start by asking your coding agent to diagnose the setup and fix what it can:

Use ADT to check my setup and tell me what, if anything, I need to fix.

The agent checks the ADT installation, project, FileMaker file, and any live connection required for the current task. See Run diagnostics and read logs to understand the report or collect its supporting logs.

Find the problem

• Installation and coding-agent problems: ADT is missing, installation failed, or a coding agent cannot find the plugin.

• The Manage Agents Option Is Missing: find the ClarisConfig.json FileMaker Pro loads, check Documents access, and confirm the required preview version.

• File access, credentials, and native operations: a file cannot be opened, an account is refused, or a FileMaker operation fails.

• Components and Web Viewer connection problems: ADT components are missing or stale, or Agent Access is not enabled or not answered.

• Type generation and data validation problems: Typegen cannot read a layout, generated types are stale, or runtime data fails validation.

• Build and runtime problems: the app does not build or behaves differently inside FileMaker.

• Errors and diagnostic messages: look up an exact message and its next step.

• Collect information for support: gather versions, logs, and reproduction details for a report.

Actions that need you

The coding agent can handle most diagnosis and repair. It may ask you to act when ADT cannot control the FileMaker Pro interface or change a sharing setting. Common examples include dismissing a FileMaker dialog, answering the grant prompt after a FileMaker Pro restart, enabling Agent Access, restarting an application after installation, or enabling FileMaker sharing for an open file.