Source Board

<Line Item 1> Name

<Line Item 2> Address

<Line Item 3> Tel No

Destination Board

<Line Item 1> Column-Name, Column-Address, Column-Tel No

I am currently facing one persistent automation-related problem with the way I manage website development tasks on monday.com, and I am hoping someone can help me understand what might be causing it. The specific issue is that when a new website development task is created or updated through my normal workflow, the automation does not always move the item to the expected status, even though the trigger conditions appear to have been met. The automation works correctly for many items, but occasionally an item remains in its previous status instead of being moved to the next stage. For example, a website task can receive the required update indicating that development work has reached the next stage, but the corresponding status column remains unchanged. The item itself is still present on the board and the activity history shows that the expected update occurred, so I am trying to understand why the automation sometimes does not perform the final status update.

The board is used to track ongoing website development work, and I have configured an automation that watches for a specific change to an item and then updates its status accordingly. The workflow is intentionally simple because I want the status column to accurately reflect the current stage of each development task. When the automation works, the behaviour is exactly what I expect: the triggering change occurs, monday.com recognises the condition, and the status is updated automatically without requiring manual intervention. The problem occurs only with some items, where the trigger appears to happen but the expected status change does not follow. I have checked several affected items individually and confirmed that they contain the same relevant information as items for which the automation worked correctly. Because the same automation can successfully process one task and apparently skip another under similar circumstances, I am trying to determine whether there is something about the timing or processing of the automation that I am missing.

I have been reviewing the automation activity and item history to determine whether the automation is actually being triggered when the problem occurs. The board records the underlying item changes, so I can see that the condition used by the automation has occurred. However, the expected status update is sometimes absent from the item history. I have also compared successful and unsuccessful items to see whether there is a difference in the sequence of changes immediately before the automation should run. In some cases, multiple item changes happen relatively close together, and I am wondering whether an automation can process an earlier state before a later update has been fully registered. I have not confirmed that this is the cause, though, and I do not want to assume that the issue is simply related to timing without knowing how monday.com queues and processes automation events.

The issue is particularly noticeable when several website tasks are being updated around the same period. Most items eventually reach the correct status, but an occasional item remains unchanged even though its triggering condition appears to have occurred. I have checked the automation configuration and have not intentionally changed the recipe or conditions while troubleshooting. I have also made sure that the affected items are located on the correct board and use the expected status column. The automation does not report a clear error to me when an item fails to update, which makes it difficult to determine whether the action was never executed, was delayed, or was executed but failed for some reason. I have started recording the time of the triggering change and comparing it with the automation activity so I can determine whether affected items follow a consistent pattern.

I have also tried manually reproducing the behaviour using test website tasks rather than changing important production items. When I make the triggering update and allow the automation to process normally, some test items transition correctly while others can remain in the original status. I have tried spacing the updates apart to see whether the issue only occurs when multiple changes happen quickly, but I have not yet found a reliable condition that causes the automation to fail. I am therefore interested in understanding what information monday. com provides for diagnosing an automation that appears to trigger inconsistently. In particular, I would like to know whether there are execution logs or automation run details that can show the exact trigger detected, the action attempted, and any reason the status update was not applied. I want to collect this information before redesigning the workflow because the current automation is otherwise functioning as intended.

I would appreciate guidance from the monday. com community on how to systematically troubleshoot this specific problem where an automation responsible for updating the status of website development tasks works correctly for some items but occasionally leaves another item in its previous status after the trigger condition has occurred. I would particularly like to know which automation execution details, item activity information, board configuration settings, or timing considerations I should inspect when an affected item is found. If there are recommended ways to prevent missed automation actions when several item updates occur close together, I would also appreciate advice on the correct approach. My goal is to make this single status-update automation reliable so that every website development task that satisfies the defined trigger consistently receives the expected status update without requiring me to manually check the board and correct individual items afterward.

Examples could include:

• Auditing account structure and workspace configuration against best practice.

• Identifying inactive users, unused boards, duplicate workflows, and governance risks.

• Recommending improvements to permissions, ownership, automations, and account organisation.

• Highlighting adoption trends and areas where teams may need additional enablement.

• Providing administrators with proactive maintenance and optimisation recommendations.

As monday.com adoption grows across organisations, AI-powered administrative agents could become a valuable tool for maintaining a healthy, well-governed, and scalable environment whilst reducing manual overhead for platform owners.

Is this something that is already being worked on?

The ask: Please allow users to drag and reorder pinned sidebar items so they can place their most-used tools exactly where they want them.

Why it matters: For users who rely heavily on a specific tool (e.g. My Work) alongside their boards, the inability to position it prominently in the sidebar creates unnecessary friction. The ability to reorder would make the sidebar truly personal and reduce the need to navigate through menus to reach frequently used spaces.

This is a small UX change with a high impact on daily workflow efficiency.

Suggest to add below features:

• Manual drag-and-drop sorting

• Alphanumeric sorting by project name

• Sorting by selected columns (e.g., Project ID, Priority)

Allowing users to control the row order would improve readability, reporting, and portfolio reviews, while eliminating the need for workarounds such as recreating projects.

We could use a Text field or a Formula column as a workaround, but why should we have to create a workaround when the Number column already provides the validation we need? It would be much more intuitive to have the option to control whether commas are displayed.