Skip to content
Genie logo Genie logo Genie - AI Assistant for FileMaker

Feature-Specific Troubleshooting

Troubleshoot issues related to specific modes or functions within Genie.

Preflight Not Available

Section titled “Preflight Not Available”
  • Symptoms: The Preflight Questions field is unavailable, or a message indicates it is not supported by your current coding provider.
  • Cause: Some providers (e.g., Anthropic) currently do not support the Preflight planning pass (Stage A) in CODE mode.
  • Fix: Open Settings and switch your Coding Provider to one that supports preflight (e.g., OpenAI or Google).
  • Note: Preflight is always enabled for QUERY and DATA modes and does not have a user toggle.

Local MCP Bridge: 400 / SSE fallback connection failure

Section titled “Local MCP Bridge: 400 / SSE fallback connection failure”
  • Symptoms: IDE logs show streamable HTTP invalid_http_request, SSE fallback Non-200 (400), or repeated client connect failures.
  • Cause: MCP endpoint/path mismatch, missing bearer auth header, or Local MCP Bridge disabled.
  • Fix:
    1. In Genie Settings, confirm Local MCP Bridge is enabled and status is running.
    2. Verify your IDE config uses URL path /mcp (not root-only endpoint).
    3. Verify Authorization: Bearer <token> is present.
    4. Recopy config using Copy IDE JSON in Settings.
    5. Ensure host/port match Genie (127.0.0.1 + configured port).

Local MCP Bridge: tool name rejected by strict clients

Section titled “Local MCP Bridge: tool name rejected by strict clients”
  • Symptoms: MCP client rejects or filters a tool because of name format.
  • Cause: Some clients enforce underscore-only naming.
  • Fix: Use fm_get_fields_on_layout in strict environments.
  • Note: Genie also accepts alias calls (fm.get_fields_on_layout, fm-get_fields_on_layout) for compatibility, but underscore form is the safest default.

Export Failures (CSV/PNG)

Section titled “Export Failures (CSV/PNG)”
  • Symptoms: A file save dialog appears, but the file is not written or is empty.
  • Cause: Missing write permissions for the target folder or a transient error in data generation.
  • Fix:
    1. Re-run the query or chart generation once.
    2. Ensure you are choosing a writable local directory (e.g., Documents or Desktop).
    3. Verify your computer has sufficient free space.

DATA Migration: No active plan or stale action click

Section titled “DATA Migration: No active plan or stale action click”
  • Symptoms: Chat shows “No active migration plan,” or clicking a migration action does nothing useful.
  • Cause: The prior plan was cleared, completed, or replaced by a new DATA request.
  • Fix:
    1. Start a fresh DATA request with clear migration intent.
    2. Wait for “Migration plan ready (N steps)” before using step actions.
    3. Avoid using old action links from earlier messages after starting a new plan.

DATA Migration: Step is halted after failure

Section titled “DATA Migration: Step is halted after failure”
  • Symptoms: Chat indicates the current migration step is halted.
  • Cause: A validation or execution failure stopped progression to protect data integrity.
  • Fix:
    1. Review the failure message shown in chat.
    2. Choose Retry Step if the SQL is still correct.
    3. Choose Skip Step only if you accept migration inconsistency risk.
    4. Choose Abort Plan if the sequence should not continue.

DATA Migration: Execute All not available

Section titled “DATA Migration: Execute All not available”
  • Symptoms: Chat does not offer Execute All, or the action is unavailable for the current DATA response.
  • Cause: The current pending operation is not part of an active migration plan.
  • Fix:
    1. Use Confirm or Cancel for single-statement DATA execution.
    2. If your intent is multi-step, restate the request as a migration sequence.
    3. Regenerate and confirm that Genie returns a migration plan before using Execute All.

DATA Migration: Full-table confirmation text mismatch

Section titled “DATA Migration: Full-table confirmation text mismatch”
  • Symptoms: Genie rejects a confirmation attempt and requests exact full-table wording.
  • Cause: Full-table or destructive operations require strict confirmation language.
  • Fix:
    1. Re-read the confirmation requirement shown in chat.
    2. Use the provided action link or exact required wording.
    3. If full-table impact is not intended, cancel and regenerate scoped SQL.

DATA Migration: Placeholder mismatch block

Section titled “DATA Migration: Placeholder mismatch block”
  • Symptoms: Chat shows a placeholder/parameter mismatch block and execution does not start.
  • Cause: SQL placeholder count does not match supplied parameters.
  • Fix:
    1. Regenerate SQL with concrete literal values when appropriate.
    2. Or regenerate with a complete parameter list that matches placeholders exactly.
    3. Retry execution only after the mismatch warning is cleared.

DATA Migration: CREATE INDEX is blocked

Section titled “DATA Migration: CREATE INDEX is blocked”
  • Symptoms: Chat shows a DATA policy or validation block for CREATE INDEX.
  • Cause: Genie does not allow CREATE INDEX in DATA mode because FileMaker manages indexing through field and storage settings.
  • Fix:
    1. Remove the CREATE INDEX request from the DATA workflow.
    2. Open the relevant table or field settings in FileMaker to manage indexing there.
    3. Re-run the DATA request only for the remaining supported schema or data changes.
Section titled “Related pages”