Rocketlane provides robust automation capabilities to streamline workflows and improve efficiency. This article explains how Rocketlane determines the execution order of automations and how users can identify the source of automation-triggered updates.
Overview of Automation in Rocketlane
Automations in Rocketlane can be configured at different levels, including global (workspace-level) automations and task-level automations. Understanding how these automations interact and how to trace their actions is essential for effective project management.
Precedence Rules for Automations
When both a global automation and a task-level automation are configured to run at the same time, Rocketlane prioritizes the global automation. The system executes global automations first, followed by task-level automations, with a minor delay between the two. This ensures that workspace-level rules are applied before task-specific rules.
Identifying Automation Sources via Activity Logs
Rocketlane’s activity log provides detailed information about automation-triggered updates, allowing users to identify the source of changes. Here’s how to distinguish between updates triggered by different types of automations:
- Form (Template-Level) Automation Updates: If a task assignee update is triggered by a form submission (template or project-level form automation), the activity log will display the user who submitted the form as the actor responsible for the change.
- Global (Workspace-Level) Automation Updates: If the update is triggered by a global automation, the activity log will show “Automation bot” as the actor for the change.
By reviewing the activity log, users can easily determine whether a task update originated from a form-level or global automation.
Practical Tips for Managing Automations
- Regularly review your automation configurations to ensure they align with your project goals.
- Use the activity log to monitor and troubleshoot automation-triggered updates.
- Prioritize global automations for rules that should apply across the entire workspace, and use task-level automations for more specific, localized actions.