Common Reasons for Automation Failures in Rocketlane and How to Resolve Them

Automation in Rocketlane enables streamlined workflows by triggering actions like email notifications when specific conditions are met. However, occasional issues may arise due to misconfigurations or unmet criteria. Below, we outline typical causes for automation failures and offer practical solutions.

Email Automation and Status Change Triggers

A frequent issue occurs when automations are designed to send emails upon project status changes but fail to trigger. This often happens when the trigger condition is set incorrectly. For example:

• Issue: If the email automation trigger requires a status change from 'Anything' to 'Completed' but the status is already set to 'Completed,' the automation won’t activate.

• Resolution: Update the trigger condition to reflect a status change event (e.g., 'Anything' to 'Completed') rather than a static value like 'Completed.' This ensures the condition is dynamically met.

Understanding Email Automation Recipients

Another concern users have is tracing which recipients received an automation-triggered email:

• Key Insight: Once email automation is triggered, its recipients can be tracked via backend systems in Rocketlane. However, it is important to note that emails already sent cannot be retrieved or recalled.

Configuring Automations with Conditional Logic

More complex automations may depend on multiple conditions being satisfied. For instance, the automation may fail if any dependent fields are not set correctly:

• Scenario: An automation designed to capture a de-escalation date fails when the project's completion status aligns, but the required 'Is account at risk?' field is set to 'False.'

• Resolution: Ensure that all required conditions are fulfilled simultaneously. In this example, setting 'Is account at risk?' to 'True' and leaving the 'De-escalation Date' field empty before marking the project as 'Completed' enables the automation to proceed properly.

Best Practices for Automation Configuration

Follow these guidelines to avoid common pitfalls:

1. Define Broad Trigger Criteria: Avoid overly restrictive conditions that limit automation activation.

2. Test Automations Thoroughly: Use test projects to validate that triggers and conditions behave as expected.

3. Check Dependencies: Confirm that values in all relevant fields align with automation requirements before initiating workflows.

Troubleshooting Automation Failures

If an automation fails to trigger as expected:

1. Review Trigger Conditions: Verify that the conditions are set correctly and dynamically reflect changes.

2. Check Field Values: Ensure that all required fields meet the specified criteria simultaneously.

3. Consult Backend Data (if necessary): For email automations, verify recipient details to ensure successful execution.

Following these steps and guidelines should help resolve common automation issues in Rocketlane efficiently.