I’m currently finalising a full sales tracking system within Monday. Have it about 99% completed but noticed a strange issue that I can’t yet explain. I’ll try to get this to make sense…
Board 1 - Opportunity / Quotes
Board 2 - Sales Managers
Board 3 - Orders
So the basic flow is an opportunity is raised and given to the sales team. They raise a quote and then send it to the Sales Manager (status trigger move). The Sales Manager then approves the quote and gets the customer to accept it. They then send it via status automation to the Orders board
Now my issue is that they trigger this by changing “Request OA” to “Requested” before it leaves the board
Once the Orders team have processed the OA request, they trigger “Send to S.M” which changes the Request OA column to Received before moving back to the Sales Manager board
So the weirdness starts here
When the pulse left the Sales Manager board, Request OA was Requested. When it comes back in, it’s Received. BUT… something is changing the status back to Requested (which then triggers the automation to move it back again to the Orders board)
I’ve disabled all automations and this reverting of the status still happens
Does Monday remember previous statuses when moving between boards???
Put together a short vid to show what I mean. You’ll see the status change from Requested to Received but then leave the board, get changed and come back in again
We had a similar experience with a status reverting back after an automation ran. Currently, the automation is set to trigger following the click of a button. The automation will then input a date, change a status and then move the item to another board. We noticed the status would change when the automation ran but following the move to another board it would revert back to its original status. We solved this by separating the automations and creating two. That shouldn’t need to occur, however, and it seems there’s a glitch somewhere. I haven’t created two separate automations yet across all the boards because that would be too time consuming and have been hoping something got worked out from monday in the interim.
Hey everyone! My sincerest apologies for the delay in responding to this request - seems to have fallen through the cracks
That said, this certainly sounds like strange behaviour in both circumstances. In order to troubleshoot, we will need to have a look at the automations that have been set up in the destination board (this will help us see what might be causing the item to move back to its original state). There also could be a race condition involved here, in-which 2 recipes start with the same action, resulting in race between the 2. If you can provide some screenshots of the recipes (perhaps on both boards just to be safe) that would be extremely helpful
I don’t believe a race condition is created but below are the automations on the original board pertaining to the issue. The grayed out automation is the one I separated into two actions:
Thanks for sharing these screenshots! Just to clarify the process…
Status changes to complete and item moves to the Estimating board.
(As per the automation) When the item arrives in the Estimating board, the status (phase column) is set to estimating.
Is the issue that the status column (phase column) is reverting back to complete after changing to estimating? I want to ensure I completely understand the process here - if there are any other automation recipes in the destination board, please include them thanks so much!
The screenshots below will also help clarify the issue. We have several boards to track projects in certain phases (Pipeline, Estimating…) and a project/item will move to another board when the automation is triggered by clicking a button. The issue arises when an item moves from the ‘Pipeline’ board to the ‘Estimating’ board. I am able to see the automation complete the steps and change the ‘Initial Contact’ status to complete and then move the item to the Estimating board. I will then see the item appear in the destination board and the phase will change from Pipeline to Estimating but the ‘Initial Contact’ status will then revert back to ‘Need to Schedule’.
Here is a screenshot of the original board and the destination board:
I tried to do some more digging on this glitch. I thought the default value for the column could have been causing the issue but that wasn’t the case. Upon further investigation, the activity log even displays the action was done by an automation and shows the status reverting back to its original status on the board the item came from, but we don’t have any automations set up to perform this action.
So sorry for the delay in responding! Thanks so much for providing this background super helpful - particularly the screenshot you have provided of the activity log.
That said, given that there are no automations in the destination board that triggering this change and there are no item default values set causing the value to revert this sounds buggy and something our technical team needs to investigate. Would you be happy to reach out to support@monday.com? You can simply share this thread there with some additional screenshots/context. It would also be helpful if you can send a short screen-recording demonstrating the steps you’re taking leading up to this issue (and a scan of automations across both boards) using the free online tool loom.com. Thanks so much for your patience on this - we will get to the bottom of this behaviour
Did this get resolved? I have the same issue. I have a automation triggered in one board: Click button > changes status > moves to board 2. The status reverts back when the item arrives at board 2.
No - the issue causing this wasn’t identified and corrected. Monday’s team, however, recommended we separate the automations into two triggers - 1) the status change and 2) move to another board. We had to go through each board and change the affected automations. We had done this on one of our boards as a test prior to posting here - and confirmed it worked - but I was hoping to rectify the issue without having to re-do the automations.
Sorry that you weren’t able to obtain any further clarity on this issue and that it ended up being a bit of a tedious fix. You’re welcome to share your ticket ID or email address with me via private message so I can check on the request and see whether I can gather any additional insights?
thanks so much!
