Automations give you the power to perform automated actions in response to different product activities. You can currently set up automations in Giving, Groups, People, Services, and Registrations!
You can toggle off any automations that you don't want to run. If you would like all your automations to stop running, click Pause Automations. If you want to remove an automation, click the three dots next to the automation you want to remove and select the Delete option.
You can view an automation's history within the last 32 days, reassign it to yourself, or delete it by clicking on the three dots in the top right corner of the automation.
You may see different statuses when viewing an automation's history.
Success: The automation ran on the person successfully.
Pending: The automation is still in process.
Paused: The automation was paused before the last action that would have normally triggered it, so it did not run. Click Run now to run the automation.
Failed: The automation failed to complete. You can click Details to find out why the automation failed. Click Retry to try the automation again.
If an automation had any errors or any instances skipped due to it being paused, you will also see an indicator showing the number of paused or failed instances on the automation.
If you choose to ignore a failed or paused automation instance, it will show up on the history page as Ignored and will not be included in the number of errors or paused items on the automation.
If you get an error message after applying an action, or if you notice an automation wasn't completed successfully, check for possible reasons in the appropriate sections below, based on which Planning Center products are used for the bulk action.
When you apply a bulk action or automation, the action will attempt to import anyone who has not already been imported into Services. Once the person is imported, it will then apply the action.
However, a couple of things can cause the import to fail.
If importing a person to Services causes you to exceed the number of people in your package, the import will fail.
An Administrator can require specific tags on a person's profile. Since a bulk action can only do one thing at a time, trying to import new people will fail if there are required tags.
To fix this, an Administrator can temporarily edit the tag group so that it is not required. They can then use the tag group filters within Services to find everyone who does not have a tag from that group to fix it.