Why do automations fail to trigger or execute as expected in SPARK MINDS?
Automations in SPARK MINDS are powerful tools for streamlining workflows, but they rely on specific configurations to function correctly. This article provides an overview of common reasons why automations may fail to trigger or execute as expected, along with troubleshooting steps and best practices to ensure smooth operation.
Overview of Automation Functionality
Automations in SPARK MINDS are triggered by specific conditions, such as tags, dates, or membership statuses. They execute predefined actions like sending emails or updating contact statuses. For automations to work as intended, all entry conditions and dependencies must be correctly configured.
Common Issues and Their Causes
1. Missing or Incorrect Tags
Automations often rely on specific tags to trigger actions. If required tags are missing or applied in the wrong order, the automation will not run.
Example: If a contact is added manually without the required program tag, downstream automations tied to that tag won’t trigger. Ensure the correct tags are applied at creation or added afterward.
2. Mismatched Dates
Automations that depend on dates may fail if the entered date does not match the system’s reference date.
Example: If the rank promotion date entered ('4/3') doesn’t match the system’s date ('5/2'), the automation will not trigger. Always ensure dates match exactly.
3. Changes in Membership or Contact Status
If the membership or contact status that originally triggered the automation changes, subsequent steps may stop.
Example: If a triggering membership is replaced or set to inactive, the automation will halt. Verify that the triggering membership or status remains active.
4. Testing Scenarios Not Meeting Entry Conditions
Automations won’t trigger during testing if the test contact doesn’t meet the entry conditions.
Example: If the test contact is marked as "Former Prospect," the automation won’t start. Update the test contact’s status to "Prospect" and remove prior tags before testing.
5. Missing Triggers
Automations without a defined trigger will not initiate.
Example: If no trigger is set for a checkout page’s tag, the automation won’t start after a purchase. Add the appropriate trigger to resolve this.
Step-by-Step Troubleshooting Guide
Verify Tags and Triggers:
Ensure all required tags are applied in the correct order.
Confirm that the automation has a defined trigger.
Check Dates and Timing:
Verify that all dates match the system’s reference dates.
Adjust scheduled dates/times if necessary to re-trigger the automation.
Review Membership and Contact Status:
Confirm that the triggering membership or status is still active.
Update the trigger or restore the appropriate membership if changes were made.
Test Effectively:
Use fresh test information or update the test contact’s status to meet entry conditions.
Complete all required actions, such as checkout or opt-in steps, to trigger the automation.
Ensure Include Tags Are Applied Before Triggers: Include tags must be present on the profile before the trigger event occurs. Adding them afterward will not retroactively start the automation.
Best Practices for Setting Up Automations
Plan Tag Application Carefully: Apply tags in the correct sequence to meet automation conditions.
Double-Check Triggers: Ensure every automation has a defined and appropriate trigger.
Test Thoroughly: Use realistic test scenarios that meet all entry conditions.
Monitor Membership Changes: Avoid altering memberships or statuses that trigger active automations.
Document Automation Workflows: Keep a record of tags, triggers, and conditions for each automation.
FAQs
Why didn’t my automation send the immediate text and email after a trial purchase?
This likely occurred because the automation had no trigger set. Add a trigger that fires when the checkout page’s tag is added.
Why didn’t my “1 day after” automation steps send after promoting students?
The automation uses the promotion date set on the Mass Rank as the reference point. If you promote students on a different date, the “1 day after” steps won’t trigger.
Why didn’t the GOAL 2B: Change Contact Status to On-a-Trial automation send emails?
The lead was missing the required Ignite program tag. Apply the program tag first, followed by the booked-trial tag, to meet automation conditions. By following these guidelines and troubleshooting steps, you can ensure that your automations in SPARK MINDS run smoothly and effectively.