Skip to content

Troubleshooting: First Response Checklist

Use this page before diving into the more specific troubleshooting guides.

Go to Licensing and Activation.

Check:

  • whether your paid key is active, expired, or invalid
  • whether this computer still shows an active activation
  • whether you can open Settings > General

A provider is configured, but Genie still cannot answer

Section titled “A provider is configured, but Genie still cannot answer”

Go to API and Provider Limits.

Check:

  • the provider key
  • the selected model
  • the endpoint URL for Custom / Local
  • the result of Test Connection

Genie is open, but the context is wrong or empty

Section titled “Genie is open, but the context is wrong or empty”

Start with FileMaker context.

Check:

  • Confirm the FileMaker file and name the target script exactly.
  • Check the allowed metadata if Privacy Mode is on.
  • After you change the selection in Script Workspace, click Refresh Selection.

Preview, Create or Apply is missing on a script result

Section titled “Preview, Create or Apply is missing on a script result”

Go to Create and edit scripts and Get better script results.

Check:

  • whether you are on a paid plan
  • whether Genie asked a question you still need to answer
  • whether the result is a draft to review, where Preview or Copy is available but Create or Apply is not
  • whether the context is too broad or too narrow
  • whether missing metadata, custom functions, MBS, or BaseElements references need to be refreshed, imported, enabled, or named more exactly
  • whether the target script has unsaved edits in Script Workspace; save it, then ask Genie to prepare the change again

Metadata or Local MCP data looks unavailable

Section titled “Metadata or Local MCP data looks unavailable”

Go to Local MCP Bridge and Permissions and SQL Errors.

Check:

  • the correct FileMaker file is open
  • Genie can read the file’s schema
  • the needed Metadata Explorer items are selected
  • the Local MCP Bridge is enabled and using the right port

Capture the visible error, screenshots, and the approximate time it happened, then continue with Troubleshooting and Recovery.