Reference

Troubleshooting

Resolve access problems, connector errors and incomplete transaction reads.

Access and authentication

Start with the problem you see below. An installation key identifies your agent; an approved grant gives it permission to read accounts. Check both when a read fails.

What you see	Next step
No installation configured	Register the agent, share the approval link and wait for the human to review it.
No approved accounts	Request access with the existing installation.
Pending request	Open the approval link as the human, select accounts and approve or deny. The agent must wait.
Expired or denied request	Request a new link with the same installation. This replaces any earlier pending link.
Old approval receipt	Check current grants and accounts; the original grant may have expired or been revoked.
Authentication failure (`401`)	Check the API origin and installation key. Restore or issue a valid key for the installation.
Grant unavailable (`403` or `404`)	List current accounts and grants. Request approval if none cover the task.

Transaction reads

What you see	Next step
`projection_changed`	Discard partial pages and restart the query without a cursor.
Invalid date range	Use UTC dates inside the snapshot window. `from` is inclusive; `to` is exclusive. Omit `to` for the latest available records.
Invalid page size	Use an integer from 1 to 100. CLI and MCP default to 50.
Incomplete or stale sync	Have the human check Accounts. Explain missing coverage in the answer.
`read_unavailable`	Retry later and explain the read failure.

MCP tool failures set isError. CLI failures exit nonzero and print structured errors to stderr. Follow the recovery guidance returned with the error.

Connector startup

Install dependencies and use absolute paths for the Node loader and MCP source file.
Check that https://vantage.ailuminare.ca opens in your browser. For a local development stack, run make health.
Set VANTAGE_API_URL to an API origin without a path, query, fragment or embedded credentials. Remote origins require HTTPS.
For credential_deployment_mismatch_use_separate_config, select the installation file for that API origin or use a separate file for the other deployment.
Store keys in regular credential files with mode 0600.

Signup, approval and deletion

If sign-in fails after signup, try signing in again. A duplicate email or uncertain network result may also mean the account already exists.
If approval fails and the outcome is unclear, reload the request status before retrying.
If the link expires while you connect a bank, ask your agent for a new approval link.
If deletion is pending, select Retry bank-data cleanup in Accounts. Reconnect once deletion is complete.

Open Accounts

Updated October 4, 2026