Feature-Specific Troubleshooting

Troubleshoot issues related to specific tasks or functions within Genie.

A paid feature is unavailable

Symptoms: Genie gives human-readable steps but no Create or Apply, or a layout, data, Auto apply, or Workbench action is unavailable.
Cause: These actions require a paid plan, and this computer is on the Free plan or its activation is not active.
Fix: Open Settings > General and check your plan and activation key. See Licensing and Activation.

Symptoms: IDE logs show streamable HTTP invalid_http_request, SSE fallback Non-200 (400), or repeated client connect failures.
Cause: MCP endpoint or path mismatch, missing bearer auth header, or Local MCP Bridge disabled.
Fix:
1. In Settings > Local MCP, confirm Local MCP Bridge is enabled and running.
2. Check that your IDE config uses the URL path /mcp, not the root.
3. Check that Authorization: Bearer <token> is present.
4. Copy the current setup snippet again from Settings > Local MCP.
5. Make sure host and port match Genie (127.0.0.1 and the configured port).

Symptoms: Claude Desktop starts but Genie tools and resources do not appear, or Claude logs show a stdio server exit.
Cause: Claude Desktop cannot use Genie’s local Streamable HTTP endpoint directly from claude_desktop_config.json; it needs the Claude Desktop stdio bridge snippet.
Fix:
1. In Settings > Local MCP, choose Claude Desktop (stdio bridge).
2. Copy the snippet into Claude Desktop’s developer config.
3. Confirm npx can run mcp-remote@latest.
4. Keep Genie running with Local MCP enabled, then restart Claude Desktop.

Symptoms: Cursor, Codex, Claude, or another MCP client sends fmxmlsnippet for plain English script requests.
Cause: Script staging should use Script Schema through fm_stage kind:script. XML is for requests that already include complete Script or Step XML.
Fix:
1. Ask the agent to call fm_session again.
2. For a new script, use fm_search to find Script Schema and the needed steps, then call fm_stage kind:script with result_type: "new_script".
3. For an edit, read the exact content with fm_read target:script (or genie://context/scripts), then call fm_stage kind:script with result_type: "delta_edit". merge_ready:false does not block staging.
4. Use fmxmlsnippet only when the request includes complete Script or Step XML.

Symptoms: An MCP client says Genie needs metadata for words like URL, API, JSON, or an external service name such as Asana.
Cause: Metadata is only needed for real FileMaker references. Words about an external service are not FileMaker metadata.
Fix:
1. Ask the agent to stage the script request again with fm_stage kind:script.
2. Use fm_read target:selection only when the prompt names exact FileMaker tables, fields, layouts, scripts, custom functions, value lists, or ExecuteSQL schema references.
3. Keep fm_query for read-only SELECT work, not for Insert from URL script generation.

Symptoms: An MCP client tries to learn field lists or relationships by running SELECT queries.
Cause: fm_query is only for reading row data.
Fix:
1. Use fm_read with an exact table, field, layout, or relationship_summary target to read the structure.
2. Use fm_query only after the schema is known and the request needs row data.
3. For data changes, pass a metadata_selection bundle from fm_read target:selection to fm_stage kind:data.

Symptoms: Genie asks one concrete question instead of giving a script or a final answer.
Cause: Genie could not tell the intent, the target, the metadata it needs, the scope of a destructive change, or whether the change can be applied.
Fix:
1. Answer the question in the chat.
2. Name the target script in your request, or select relevant references in Metadata Explorer. Genie reads the exact script content when needed.
3. If metadata is missing, refresh or select the relevant items in Metadata Explorer.

Symptoms: A file save dialog appears, but the file is not written or is empty.
Cause: Missing write permission for the target folder, or a temporary error while preparing the data.
Fix:
1. Run the query or chart again once.
2. Choose a writable local folder, such as Documents or Desktop.
3. Check that your computer has enough free space.

Symptoms: The chat shows a placeholder or parameter mismatch and the change does not run.
Cause: The number of SQL placeholders does not match the values supplied.
Fix:
1. Ask Genie to prepare the SQL again with literal values where that makes sense.
2. Or ask for a complete parameter list that matches the placeholders exactly.
3. Run the change only after the mismatch warning is gone.

Symptoms: The chat blocks a CREATE INDEX request.
Cause: FileMaker manages indexing through field storage settings, so Genie does not run CREATE INDEX.
Fix:
1. Remove CREATE INDEX from the request.
2. Manage indexing in the field’s storage options in FileMaker.
3. Ask again for the remaining schema or data changes.

Symptoms: the rows under Your own agent are greyed out, the footer under the composer says Local connection off, or a reply fails with a message about the engine.
Cause: Local MCP is off or not running, Local MCP Privacy Mode is on, the program is not installed or not signed in, or it is out of date. These messages have no numeric code.
Fix: click Turn on if you see it, turn Privacy Mode off for Local MCP, or use Install, Connect or Update on the card in Settings > Models. Every message and its remedy is listed in Claude Code and Codex.