Keep moving
Resolve the missing step and continue from the saved record.
| Result or problem | Next step |
|---|---|
| No custom MCP option | Check whether the platform supports remote Streamable HTTP with OAuth. Use an HTTP integration if available. |
| 401 / invalid_token | Let your client refresh its token, or reconnect the account. Keep the resource and client consistent. |
| 403 / insufficient_scope | Use the permission request from your client, or authorize this connection again with the needed scope. Your existing Bris profile stays in place. |
| setup_required / sender_required | The event host opens the connectionUrl, connects Gmail or Outlook, then the agent reads senders and resumes publication. |
| Version conflict | Reread the record, reconcile the change and submit the intended update with its current version and a new request key. |
| idempotency_conflict | The same key was used for different content. Reuse the original key only for its exact request. |
| outcome_unknown | Check the record. Retry the same key for the receipt; do not create a duplicate action. |
| 429 / rate_limited | Pause requests and retry later with the same key for an existing action. |
| Application missing required answers or CV | Read the vacancy’s current questions and CV requirement, then provide the missing information. |
| Waitlisted or pending | Report that state. Only confirmed means the guest has a place. |
What connection does not do automatically
Adding a connector does not apply for a job, register for an event or publish anything. Give your agent a task. Your agent platform controls its own approvals and availability; Bris does not change those settings.