Salestrekker 2.0 allows you to create automation chains, where one automation triggers another based on specific criteria. This feature enhances workflow efficiency by linking automated actions together. However, it’s essential to understand how to manage these chains to avoid unintended loops or breaks in the automation sequence.
Automation Chains: How They Work
Creating Automation Chains
Automation chains in Salestrekker 2.0 are designed to enable a series of automated actions to occur sequentially. For example, one automation can trigger another when a specific condition is met, creating a seamless workflow across different stages of deal management.
Example Workflow: An automation is set to change a deal’s color to purple. Another automation is triggered when a deal’s color is purple, moving the deal to another stage. You can chain multiple automations this way to create complex workflows.
Can Automations Create an Infinite Loop?
No they cannot. This has been considered and needed mechanism implemented for this not to happen. An infinite loop would be when an automation’s end condition serves as the trigger for the initial automation, causing the chain to repeat indefinitely.
Why Infinite Loops are Not Possible
Salestrekker 2.0 prevents infinite loops by restricting any automation from being re-triggered within the same chain. If an automation sequence attempts to re-trigger a previously executed automation within the chain, the sequence will stop to prevent an endless loop.
Scenarios for Automation Chains
1. Complete Chain without Loop:
Scenario: Seven automations are set up in a sequence where each one triggers the next (1st triggers 2nd, 2nd triggers 3rd, and so on until the 7th).
Outcome: The chain completes successfully and no automation in sequence was set to initiate any of the previous.
2. Chain Attempting to Loop Back:
Scenario: Seven automations are set up, but the 7th automation is designed to trigger the 1st automation once again.
Outcome: The chain executes from the 1st to the 7th automation, but when the 7th tries to trigger the 1st again, the system recognizes the repetition and stops the sequence, preventing a loop.
3. Mid-Sequence Loop Attempt:
Scenario: A chain where the 4th automation triggers the 2nd one again.
Outcome: The chain progresses through the 1st, 2nd, and 3rd automations, but when the 4th tries to re-trigger the 2nd, the system detects the repetition and halts the chain. Automations 5, 6, and 7 do not execute.
Troubleshooting Automation Chains
To effectively manage and troubleshoot automation chains, consider the following:
Double-Check Automation Sequences: Ensure that no automation in a chain is set to trigger a previously executed automation within the same sequence.
Monitor Workflow Changes: Refresh your workflow to see changes applied by automations. Automations may not appear immediately due to system refresh rates.
Use Activity Logs: Each automation action is logged in the deal’s activity log. Review these logs to track the execution flow and identify where any issues may have occurred.
Common Issues and Solutions
Automation Not Executing: Check if the automation sequence is trying to re-trigger an already executed automation. If so, modify the sequence to avoid this.
Changes Not Visible: Ensure you refresh the page to view the latest updates made by automations.
Incomplete Chain Execution: Verify that all conditions and triggers are correctly set and that no part of the sequence is inadvertently blocked by a repeating trigger.