Contact
Email contact@trieflow.com. Include your QueryFleet version, macOS version, connection type, and exact on-screen error.
Never send passwords, tokens, connection strings, database contents, or confidential queries.
Support
QueryFleet support for operators shipping real database work
QueryFleet support stays precise about the app version, the connection you were using, and the exact screen state that failed.
What To Include
Faster triage starts with the right facts
Support requests move faster when the report identifies the failing workflow instead of only naming the product.
Connection tests
Confirm the driver, host, port, database, and authentication method, then capture the exact connection test error if QueryFleet cannot connect.
Capability labels
Report whether the connection was labeled connect, browse, understand, or operate so support can match the workflow to the engine's shipped support boundary.
MCP setup
If a local AI tool cannot reach QueryFleet, include the MCP client name, the selected policy mode, and whether the issue occurs during discovery, schema inspection, or query execution.
Redis Pub/Sub local listener
For Redis Pub/Sub issues, say whether the embedded view reached the IPv4-loopback-only local listener and whether the failure happened before or after you selected Connect.
Mac App Store billing
Billing and refund questions should include the Apple ID region and the App Store receipt state shown on your Mac so Trieflow can distinguish store-account issues from app issues.
Sensitive Data
Keep secrets and customer data out of support mail
QueryFleet support can usually diagnose a problem from environment details, screenshots, and exact error text without receiving privileged material.
Do not send
- Passwords or API tokens
- Connection strings or private hostnames
- Database contents or production exports
- Confidential queries, prompts, or customer data