question Issue with Decision table in Workflow Automation forum

Issue with Decision table

VenkatakriC3227 — Wed, 15 Apr 2026 15:26:20 GMT

Hi Community,

I was working on the Decision tables, as I am building it and publishing it couple of times again and again. I realized there is bug with syncing between flow designer call and decision table.

The bug is, I have put some condition checks in decision table and published it. and then I've added the make a decision step in flow designer and called this decision table. Now I have one more condition to add to decision table, but the result is going to same. so, I have just made the change to existing row in decision table, now it giving one more resulting branch in flow designer. I have take configure some action under this new same result branch, which does make any sense.

Please let me know your thoughts here or educate me If I misused it.

Thank you so much

Re: Issue with Decision table

TharaS657398130 — Thu, 16 Apr 2026 08:55:01 GMT

Hey

This is not really a bug, it’s just how Decision Tables work with Flow Designer: when you first add a Make a decision step, Flow Designer stores that version of the table, and if you later edit or republish the decision table—even if the result looks the same—it may treat it like a new outcome and create an extra branch; that’s why you’re seeing duplicate result paths.

The simple fix is to refresh or re-add the decision step in Flow Designer, and going forward, try to keep your decision outputs stable (don’t keep changing result values) and only update conditions to avoid this confusion.

Re: Issue with Decision table

VenkatakriC3227 — Fri, 17 Apr 2026 06:02:57 GMT

Hi @TharaS657398130, Thank you for your response.

I did not change result actually but the conditions. It still created a separate branch for the same result.

Ex:
Conditions: name is venkat

Resulting Branches: Answer = true

After I make a change condition which would like below:

Conditions: name is venkat or name is krishna

Resulting Branches: Answer = true

Answer = true

but versioning part makes some sense why it is returning the same resulting branches.

I have an idea now. Before I make changes to decision table, I will delete decision flow from Flow designer and make changes and publish the decision flow. and then call it again in flow designer. I hope this works. But still lot of re-work for just adding one more condition to existing one.

Re: Issue with Decision table

TharaS657398130 — Mon, 20 Apr 2026 10:15:59 GMT

If you found the answer helpful please upvote and mark it as solution

Thank you