nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does my automation wont work, even if the conditions are applied?

Christophe Ventura

Hello,

I got some Problems with my automatisations. I made a workflow where the automations should apply to ( in my Pictures you will see examples). To the workflow i got a list of my single plans, that should get automated.
The Status of my underproject should automaticly update when i made changes to the List. But it doesnt, it doesnt even start the automatisation( what i can see in the Audit-Protokol)
Now i cant answer myself why it doesnt start.
Downstairs you can see the start of my workflow and the first part of my list including the automations.
The first automation, should be that he checks, if some changes are made to the first slot, so if a Date is put/changed it should change the Status to "Demande de Raccordement signée". If you can see the Status is still on the the first status even i put 2 conditions already in, so it should already be on the 3th status. but it doesnt even start the automations. Do you have any solution for that? What did i make wrong on this automatisation? I put so many hours into automatisation already, but cant find any solution

thank you for any help 😊

Liste .png DdR_signé__Preisanfrage.png DdR_signé__Vertrag.png

Accepted answers

All comments

Christophe Ventura

Workflow 50%.png Demande de Raccordement_DdR signé.png

I uploaded my Workflow and my first automatisation again, cause it got deleted i dont know why

Bill Sheboy

Hi @Christophe Ventura -- Welcome to the Atlassian Community!

By default, the actions of one rule do not trigger other rules. This is to prevent errors and runaway recursive looping, which potentially would lead to all rules halting due to "throttling" conditions.

When you intentionally want the actions of one rule to trigger another, enable the following setting in the rule details only in the downstream rule:

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

Kind regards,
Bill

Christophe Ventura

Hey @Bill Sheboy Thank you for your answer. The problem is not that one rule should trigger another. its the fact that all my rules should start indiividual. At first if i put a date on the first box i called "Demande de Raccordement" the status should change to that.

If the second box got a date it should trigger the second rules and update to the next status to the next workflow on the list.

So i dont get it why it doesnt do it.

Best Regards

Bill Sheboy

Which rule does not trigger as you have posted several images?

Please post an image showing the audit log details for that rule.

What is the type of field you are changing?

How are you changing the field: entering a value manually, or some other method?

Please post an image of an example issue with these fields.

Christophe Ventura

So i explain it again its simpler, maybe i explained it too complicated.
So i got my List check picture below:

In this List i input 2 Dates manually in the red box. The first date is a condition and a rule.

When i first change the date on the first box so the date on the left this rule should apply:

i put the trigger into, if value of the first date slot is change --> when this slot isn't empty --> Status change to "Demande de raccordement signée". This rule doesn't appear on the audit log, even if i put the Date in manually, the rule wont trigger.

2. After this i apply a date into the second case you can see in the red box. This date is also put in manually. This two rules should apply:

Both of them also dont appear in the audit-log, even i apply the date in the second slot.
There also the rule is: if the Value of the second slot is changed, apply the following condition.

So i dont really know what i did wrong. If you need any more info, let me know.

Best Regards

Christophe

Bill Sheboy

Regarding the images you show in #2, why do you you have two rules with the same trigger and conditions, but which transition to two different status values?

Where are the issues located that you are changing? Are they in the project Task-Planer, which is where the rules are defined?

Christophe Ventura

Yes, its because i want 2 conditions to trigger when i put a date in a certain box.

But the problem starts already on the first condition, it already wont update the status on the first condition, and thats my problem

Bill Sheboy

As an aside, there is clearly something not working in the community site with this thread as it keeps splitting answers in a single thread into different ones. Perhaps a community leader is moving it back and forth between "discussion" and "question" type. Regardless of that...

I recommend pausing and merging those two rules into a single one, and use an if / else block to handle the differences. As I noted, both rules have the same trigger but change the same fields (such as Status) to different values. This could cause a "race track error", where the rules are competing to make the updates.

Once you have merged to the minimum number of rules, re-test your scenarios, and it is not working, post the following in this same thread:

an image of the complete rule
an image showing the audit log details for the rule execution
explain what is not working as expected.

Bill Sheboy

Hi @Christophe Ventura

I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks!

Kind regards,
Bill

Julian Governale

I believe your operation is incorrect for your field value change trigger. If I translated it correctly, your rule will fire only when the field is edited during a transition.

You just want your rule to fire when the field is edited and then the automation to do the transition.

I would start there for troubleshooting getting the rule to fire.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

automation