Fix a blocked workflow

Connected, but tools return 401

1. Check that the MCP server URL is exactly https://mcp.graviola.dev/api/mcp.
2. Complete OAuth in the same client that will execute the tools. In OpenCode, use opencode mcp auth graviola.
3. Select the account and workspace containing the records you need.
4. Run workspace_status and usage_get. A transport connection or tool list alone does not prove authenticated access.

Search or reveal permission is missing

Read only access cannot search external data or reveal contacts. Reconnect with the access needed for the task, or create a correctly scoped API key. Workspace roles and plan limits continue to apply.

With direct execution permission, ordinary requested data actions do not need a separate review every time. Limited access can return an exact action review. Do not have an assistant approve a human review on your behalf.

The result list is empty

1. Read the saved result and its selection reasons before starting another search.
2. Check whether the role was actually included in filters, not only in the query label.
3. Separate no email, unknown availability and no LinkedIn.
4. Load a stored profile by its returned reference if professional evidence can still be completed.
5. Only widen a mandatory requirement when the user chooses to. Viewing incomplete saved results does not itself require a new search.

Profile loading fails

A service or access error does not prove the person has no career history. A loaded profile without dates also does not prove the required years of experience.

Stop repeated sibling requests when the same data service or permission failure occurs. Keep the search and references. An old request recorded as uncertain needs recovery; changing the profile ID or starting another search is not a safe repair.

Record not found or approval belongs to another account

Check the selected workspace and signed in email. A candidate ID, saved search ID, profile ID and requestId have different purposes. Use the returned next action rather than substituting IDs.

An approval is bound to the exact account, workspace and action. Do not recreate or approve it under a different identity to work around access control.

No email arrived

1. Confirm a paid plan and an authorized sender mailbox.
2. Check whether the sequence is a draft, active or paused.
3. Check the recipient, timezone, sending window and shared mailbox capacity.
4. Read sequence activity for queued, accepted, blocked, failed or uncertain jobs.
5. Do not assume accepted means delivered, and do not repeat an uncertain send blindly.

What to send support

Share the action, approximate time, workspace name, error message and a request reference if available. State whether credits changed. Remove API keys, tokens, verification codes and unnecessary personal data.