Triggering Autopilot from the UI

You can assign Autopilot to a request one at a time from the ticket itself, or to many requests at once from the Requests table. Both methods check each ticket's eligibility before assigning it — see Autopilot Overview for the eligibility requirements.

Assigning Autopilot to a single ticket

1. Open the request you want to automate.
2. Click Put on Autopilot, near the top of the ticket. This button is only enabled when the ticket meets Autopilot's eligibility requirements; otherwise it's greyed out with a tooltip explaining why.
3. Confirm the assignment in the dialog that appears.
4. Autopilot is assigned to the request, and the ticket updates to show that Autopilot is now handling it.

Assigning Autopilot to multiple tickets at once

1. Go to the Requests table.

2. Optionally, use the filters to narrow down the tickets you want to automate — for example, by right (Delete my data), country, or brand.

3. Select the checkboxes for the tickets you want to run on Autopilot.

4. Click Put on Autopilot in the action bar at the bottom of the screen.

   

5. Confirm the assignment. MineOS checks each selected ticket individually: eligible tickets are assigned to Autopilot, while ineligible ones — for example, tickets with manual tasks in their workflow — return an error, so you know which ones still need manual handling.

Retrying Autopilot after an error

If Autopilot can't complete a request, the ticket shows an Error running Autopilot badge. Hover over it for details, and check the ticket's audit log to see what failed.

1. Open the request and fix the cause of the error.
2. Click Try again next to the error badge. The button is greyed out if the ticket no longer meets Autopilot's eligibility requirements.
3. Confirm in the dialog that appears.

Autopilot re-runs only the integrations that haven't finished. Integrations that were already completed or in progress when you confirmed won't run again.

To retry several requests at once, select them in the Requests table and click Put on Autopilot. The same rule applies to each selected request.

After you assign Autopilot

Once a ticket is successfully assigned, an indicator appears next to it in the Requests table and on the ticket itself, so you can tell at a glance which requests Autopilot is handling. You can still open and review a ticket manually at any time, even while it's running on Autopilot.

If the request has a waiting period before processing starts, a Waiting period banner appears on the ticket with a Stop Autopilot button. The button is hidden while the request is marked as Required Attention.

If you'd rather not assign Autopilot request-by-request, you can also set up an automation that assigns it to every new eligible request automatically as it comes in.