Collect information for support

Collect one package of evidence that identifies the environment, the failing task, and the first error. Do not include passwords, tokens, record data, or other sensitive FileMaker content.

Ask the agent to gather it

Copy 
Gather the information needed for an ADT support report about this failure. Include the full diagnostic result, relevant logs, versions, and exact reproduction steps. Redact secrets and FileMaker data.

Include these details

  • What you asked the agent to do

  • What happened instead, including the first complete error and any structured code

  • Whether the failure repeats and the shortest steps that reproduce it

  • ADT version and build, macOS version, FileMaker Pro version, and coding-agent application and version

  • Whether the FileMaker file is local, shared from FileMaker Pro, or hosted by FileMaker Server

  • The diagnostic result for the correct project, FileMaker file, and task

  • Relevant installer logs

  • Whether restarting the affected application or re-answering the grant prompt changed the result

For a Web Viewer app, also include the app's check or build error and whether the failure occurs in browser preview, inside FileMaker, or both.

Files the agent may collect

  • Relevant files under ~/Library/Application Support/ADT/MCP/logs/

  • The affected configuration files, with usernames or private host details redacted when necessary

Do not attach the FileMaker file unless the support recipient explicitly requests it and you are authorized to share its contents.

Check the package

Before sending anything, confirm that the report excludes passwords, keychain contents, authorization tokens, customer records, and unrelated source files. Keep the original error text and timestamps because paraphrasing can remove the detail needed to identify the failure.