Automation rule triggered by another automation

Currently there is a rule where: "Automation rules won't be triggered in case the changes to tasks or projects are made by another automation rule."

I would like for this to be a possibility to, for example, move a project once completed/canceled automatically, and then move the project again automatically if the status does not change in X amt of days. The applications are numerous, but the example I just described is for compliance purposes - deleting associated files in a project to adhere to our clients data retention policies.

Having automations trigger off of another would increase efficiencies by eliminating manual processes. Is it possible to turn the above rule on/off?

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Elizaveta Bogdanova

Welcome to the Community @Ryan Davis, and thank you for sharing your feedback on Wrike's Automation!

It's not currently possible to disable this, so we'll record your feedback and pass it on to the Product team. Thank you for posting!

Adam Pfeifer

+1 this seems like such an easy win.

James Ackerly

Agreed! There are so many posts in this feedback section relating to being able to trigger automations from automations. Unfortunately that means no one post has a lot of votes.
It seems like such as wasted opportunity that could dramatically improve efficiency. Every time we look to automate a business workflow, we find barriers in Wrike's automation process related to this deficiency. We have to rely on people taking manual actions for the simplest things, and that's where errors and delays come from.
A recent example I have - I wanted to automate an approval workflow to purchase requisitions.
I created a form, gather a dollar amount, create a task and use an automation to assign approval statuses based on that dollar amount. I have certain approvals assigned to each status depending on the dollar value.
Wrike creates the task beautifully and even assigns the correct status. However, the approvals are not added to the task because it was done through automation.
Now I have a workaround in place for an automated comment to be made directing the assignee to choose the appropriate status to kick off the right approval chain (it works if they manually do it of course). If they choose the incorrect status, a lot of work can result that would later need to be redone.
It makes no sense to have a manual step when the automation capability is there in Wrike - they just need to allow it!

Elizaveta Bogdanova

Thanks for the detailed feedback @James Ackerly! No updates from our side here, but I'll share your feedback with the Automations team 👍

Connor Redalen

It seems like Wrike really doesn't want to allow its users to effectively automate things, not having dynamic assignments within automations and not allowing automation rules to relate to each other leaves Wrike's automation capabilities at a preschool level at best. This seems like it must be by design for some reason?

Like for some reason this even applies to things that are happening within a workflow. If an automation bot moves a tasks workflow status and that status has approvers wrike will not create the approvals.

Matthew Connell

Agreed Connor, I'd speculate it's by design to drive customers to the (exorbitant) Wrike Integrate product. The term "Automation" is a bit disingenuous if you can't trigger automations from other automations, which is pretty fundamental to the very idea of automation

Stephanie Nelson

We have also been running into this issue - ours is fairly simple. The automations are:

automation 1:
if a task has a start date within 30 days = change status to "upcoming"
(conditions: task item status currently set to "not started")

automation 2:
if a task has a start date within 5 days = change status to "on deck"
(conditions: task items status currently set to "not started" or "upcoming")

So when automation 1 runs, it won't run automation 2.. which seems kind of crazy because this feels like a simple concept. When we reached out regarding this issue, we were provided with the rule/limitation "automation rules won't be triggered in case the changes to tasks or projects are made by another automation rule."

We're hesitant to move futher with automations due to this limitation.

Giovanni De Giovanni

Hi! Following up on all the previous messages, I would like to:

Ask if there is any update from the Wrike development team, to understand whether this issue is in the pipeline or not, and when.
Ask if it is possible to "merge" the community posts that, in various ways, address this issue and request a solution (for example, I posted one some time ago: /hc/en-us/community/posts/17608996246679--Automations-Possibility-for-an-automation-to-be-triggered-by-a-change-of-state-generated-by-another-automation-not-just-manually, but there are probably others as well), so that we can increase the number of upvotes, showing that this request is highly present in the community.

Best Regards, Giovanni

Rohan V

Hey everyone 👋

Thank you for taking the time to share your detailed suggestions. We truly appreciate your input and understand your concerns. Although this suggestion isn't on the 2024 roadmap, as other priorities are currently taking precedence, rest assured that all your suggestions are being shared with the Product Team. I'll definitely keep you all updated if there's any news.

We really appreciate your ongoing feedback and support. Thank you!

Casey Teague

+1 we really need this..

Basudha Sakshyarika

Thank you for supporting this suggestion, @Casey Teague. 👍🏽

Marco Eberl

Would absolutely a benefit to be more efficient and flexible in automating tasks.
I have a rule that is triggered by a task status change. But when this status change is made by another automated rule, my rule does not get triggered.

Alan Gin

I've run into the same issue as well. Has anyone figured out a workaround for this yet?

Casey Teague

Yes we used Mulesoft to chain automations using the API. Its disappointing they don't disclose this during the sales process.

Sofia Felici

I've commented few days ago another similar community post /hc/en-us/community/posts/11407128738967-Enable-Automation-to-work-for-Tasks-Created-by-API-Import-or-Blueprint-Request-Form?page=1&no-translation-it#community_comment_34315106208407
I think these posts should be merged, since the topic seemes to be relevant

I'm sharing also here below my comment regarding this stuff:

Currently, I am unable to implement automations on all tasks in my company's projects, because all tasks are created through an automation: within the project, there is a custom field that, when flagged, ensures that all tasks (taken from various parts of different blueprints) are added to the project.

This automation is very convenient and allows us to create tasks within an already created project - which unfortunately is not possible via request forms, since in request forms it is not possible for the user to select which project to add the tasks to.

Unfortunately, however, the fact that the tasks are created automatically does not allow us to activate other automations on the tasks, which is so bad for us

Eric Lavallée

Fixing this design flaw would enable people to get rid of repetitive manual work. The purpose of automation is for things to get done automatically whenever a rule is triggered. I have a use case where I want to adjust the due date of tasks when they are overdue. Because of this limitation, the automation rule only triggers the first time the task is overdue, but never the subsequent times. It defeats the purpose of using automation altogether.

Eric

Basudha Sakshyarika

Thanks so much for your feedback, folks! No updates at the moment, but I’ve passed this along to the Automations team. 👍🏽