Configuring automations in Rocketlane to accurately capture the De-escalation or De-risked date requires understanding key triggering conditions and avoiding potential conflicts between automations. This article provides actionable guidance on setup, best practices, and troubleshooting common issues regarding automation in Rocketlane.
Automation Setup to Capture De-escalation or De-risked Date
To ensure your automations effectively capture the required dates, consider the following:
Trigger Conditions for Capturing Dates: - When the Is account at risk? status changes from True to False, set the De-escalation or De-risked date to the current date. - When a project status changes to Completed, and: - The De-escalation Date field is empty. - The Is account at risk? field is set to True. In this case, set the De-escalation Date to the project completion date.
Combining Automations: - To avoid race conditions—where multiple automations trigger simultaneously and interfere with each other—combine related actions into a single automation. This ensures consistent results and avoids missing date captures.
Purpose of Predefined Automations
Rocketlane offers specific automations to address distinct conditions:
'Capture De-risked Date': - This automation sets the De-escalation Date when the Is account at risk? field is set to False.
'Capture De-escalation for At-risk Completed Projects': - This automation sets the De-escalation Date to the project completion date when the status changes to Completed, the De-escalation Date is empty, and Is account at risk? is True.
Troubleshooting Automation Issues
Missing De-escalation Date After Project Completion: - If the automation does not trigger after project completion, check whether the Is account at risk? field is set to True. If this field was previously set to False by another automation, the condition for the automation to trigger will not be met.
Automation Fails to Capture Dates: - Race conditions could prevent an automation from successfully capturing the date if multiple automations are set up for the same trigger. To resolve this, consolidate overlapping automations into a single workflow to avoid conflicts.