Confirmations and approvals
Why some tools ask before they act, and how confirm_action and retry_action work.
Some tools change things outside Invyte or can't be undone. Instead of acting at once, they return a review: a plain sentence saying exactly what will happen, such as "Email 12 people about Senior Backend Engineer from jane@acme.com".
Your client shows you the review. Only when you say yes does it call confirm_action, which runs that exact action.
If anything changes in between, the review is refused and a new one is shown.
What asks first
- Anything that reaches people: outreach, invitations, shares, Client deliveries, Slack posts.
- Anything that can't be undone, such as archiving a Job.
- Anything that costs money, such as finding an email or running External discovery.
Repeats and uncertain results
An identical call that emails people, can't be undone or costs money returns the first run's result for 10 minutes,
so a model repeating itself doesn't act twice. If a result was uncertain (a timeout, a dropped connection), the client
calls retry_action with exactly the same values to learn what happened, never to act again.
Approvals
When Autopilot is on for a Job, it may ask before acting. Those requests wait for an approver in Invyte. Use
approvals_list and approvals_decide to see and decide them from your client.