Skip to main content
Help center / Apps & extensions / Automations FAQ

Automations FAQ

Answers to common setup and operating questions about Automations — who can use it,
how publishing and scheduling work, and what to check when a run waits.


Setup and access

Do we have to turn Automations on?

It depends on your plan. Automations is licensed and comes with Platform Standard and Enterprise: on those plans it is on until an admin disables it. On any other plan an admin enables it from Admin → Apps → All Apps. An organization that already had automations when the app was created had it switched on.

Who can open Automations?

Business admins always can. Anyone else needs to be in the app’s audience (Manage User Access) and either hold a process grant a business admin issued on Access, or own an automation. Being an admin of this app or another app gives no automation rights by itself. A grant does not give app or data permissions either; every action still checks the person’s own access.

What happens if we switch Automations off?

Its pages close, and nobody can use their access to automations until a business admin turns it back on, so an automation under process access no longer starts. An automation a business admin set up without process access keeps running, and business admins still manage it under Admin → AI Operations → Automations. Switching Loop off does not affect automations: they have their own app.


Building and publishing

Does saving an automation change what is already running?

No. The editor saves a draft. Review it on the automation’s page and choose Publish Version separately. Publishing pauses the automation’s starts and turns off their auto-approve; review their inputs and approval settings before resuming them. For an automation under process access, publishing also pauses the automation itself: resume it, and each start’s owner then renews its consent and resumes their start. Runs already started keep their saved steps and input definitions. Pausing an automation stops it from running.

Can I return to an earlier automation version?

Open Published versions on the automation’s page and choose Copy to Draft. Review and publish that draft to use it for future runs. A run’s page also offers Copy this run’s steps to the draft when the run used different steps from the current version. Neither action reverses work already performed. Older runs created before input snapshots were supported may not keep their original input definitions; check those inputs before publishing.

What happens when I install a starter?

Personal Follow-up, Reviewed Weekly Follow-up, Verified Workday Completion, Manager-approved Service Request, Weekly Team Follow-up and New-hire Access Request open editable, inactive drafts. They do not grant access, publish, run or start a schedule. Customize the draft, publish it and resume it. A schedule also needs its owner’s separate authorization.

Why does the team starter need a teammate and a scope before publishing?

A built-in template cannot choose a person in your organization. Choose the same named teammate as input respondent and Task assignee, set reporting-team scope and a people limit of at least two, and keep the required Task review. The original manager must have current Tasks assignment rights. One run addresses one teammate; it does not expand to a whole roster. The teammate’s answers can become their task text, visible through the native Tasks permissions.

Where does a service request get approved and assigned?

The employee needs their own authorized copy: a grant with “Edit process definitions” and “Run processes”, access to Automations and Service Desk, then review by someone allowed to publish before it runs. A manager’s published copy does not run as another employee.

In Service Desk, the request type owns approval and routing. Configure General or Access requests for the required manager approval and fulfillment or IT queue before publishing the matching starter. The automation will not add approval when that native policy is off. Map all required supported fields; use the native form when the request requires attachments, location or equipment fields, or a knowledge-article check. A ticket awaiting approval has not entered fulfillment, and creating it does not mean the work is complete.


Running and scheduling

Which automations can I schedule?

An automation can be scheduled from My Scheduled Starts when it is published and active, runs as you, has no Wait step, and pauses only for your answers to a top-level input step or your approval of a top-level task it creates. If you are not a business admin you also need “Run processes” and “Manage process starts” access to it. A business admin can also add a start to any automation from its starts page.

Can a scheduled automation wait for my answers or approval?

Yes, for supported personal input, input from one named teammate or current manager, and explicit Task approval steps. A team follow-up schedule runs as its original manager; the teammate answers and that manager reviews the exact task separately. Authorize the schedule separately, then open the request on desktop or phone when notified. Review your answers or the exact action before confirming. Confirming queues the rest of the run; check the run’s status for completion. Rejecting the action stops the run without performing it. Publication approval is separate from approval during a run. A scheduled run waiting for a person prevents an overlapping run of that start.

Ask AI and MCP can hand you the input page. They do not fill in your answers or submit them for you.

Can I reject with a reason, or correct a request that is waiting for the wrong person?

For a Task review, Reject and stop offers an optional reason of up to 2,000 characters. The original reviewer can see it on the decision page; notifications stay neutral. Service Desk uses its own rejection reason and decision rules. A changed or missing participant does not transfer an open request. Correct the setup, cancel the old run, then use Review process and start again to start a new one. Completed actions remain, so check existing tasks and tickets before starting again.

Why does my run still say waiting after work was created?

Creating the work is one step. The run follows the linked task or Service Desk request until its outcome is recorded, then continues the remaining steps. Ready to continue means the outcome is recorded but the rest of the run is still queued. The run request page shows who has the work now, and links it only when you can open that app and record. Cancelling the run stops later steps; it does not undo or cancel work already created.

Why is my run waiting for Workday?

The automation is waiting for Training’s completion delivery to be verified against your existing Workday Learning enrollment. A queued or uncertain delivery is not confirmation. Later steps wait, and after 24 hours without verification the run fails with an explanation. Your administrator can inspect the delivery in Training. Cancelling the run stops later steps; Training manages its delivery separately.

What does Verified Workday Completion require?

Your own completed, eligible Training enrollment, the configured Workday Learning connection with completion delivery enabled, a current worker mapping, and current Automations and Training permissions. Your administrator supplies the exact existing enrollment ID or WID and course reference: Learning_Course_ID:<course ID> or WID:<course WID>. The local course must match the unique Workday course. Ambiguous matches and course-offering references are refused. Keep credentials in the integration settings, never in the automation’s inputs. This is a manual automation step; it does not create Workday enrollments or offer approval-before-send.

Can I undo what a run changed?

A business admin can, from the run’s page. What this run changed lists each change, and Undo This Run puts each field back to what it held before the run, unless it has been changed again since. Status changes, records the run created or deleted, and anything it sent are not undone. The button shows only while a changed field can still be put back.


Controls

Where do I pause automations in a hurry?

On the Automations list, open the ⋮ menu and choose Pause All Automations. It stops every automation’s scheduled and event starts and cancels queued runs until a business admin resumes them; Run now still works, and the list shows a banner with Resume Automations while the pause holds. Business admins can pause, and so can the app’s admins who can open the Automations list (an app-admin grant alone does not open it); only a business admin can resume. To stop all AI at once, automations included, a business admin uses Pause All AI in AI Operations. To stop one person’s scheduled start, a business admin uses Stop any scheduled start in the same ⋮ menu.

How do I know whether an automation is helping?

Loop measures it. When Loop is on, the Automations list has a Result column showing the verdict of the Loop plan that measures each automation’s start. An automation with a running start and no plan shows Never measured — find out to people who can own a Loop plan; it opens one for that start.


More help

  • Ask AI — the assistant answers Automations questions from this article.