Dependencies let you connect items so that a change to one item updates what follows. When boards use multi-level subitems, a parent item’s timeline is derived from the items beneath it, and any dependent item is then scheduled from that result. 

Recently, a calculation bug affecting dependency dates was identified and fixed. Separately, a product improvement was made to block a related issue from occurring. No data was lost; your items, dates, and board history remained intact throughout.

How dependency dates are calculated

A parent item’s timeline is derived from the items beneath it, rather than being set directly. When an item depends on another item, it is scheduled based on the value stored for that item in the system, not on the value shown on your screen. In normal operation, these two values are always identical.

Timeline rollups: a stored date that didn’t match the displayed date

What happened

On some boards using multi-level subitem dependencies, a parent item’s timeline was shown correctly on the board, while a different value was stored in the system.

Items that depended on the parent were scheduled from the stored value, so they were scheduled from a date other than the one displayed. That difference carried forward to every item further along the dependency chain. Because the dates shown on the board were correct, the difference was not visible from the board itself.
 

What was corrected

The calculation has been corrected. The displayed value and the stored value now always match, so dependent items are scheduled from the correct date. Additional validation was added to the rollup calculation, and monitoring is in place to confirm the behavior remains stable. No action is required for work created from this point onwards.
 

Boards created before the correction

Boards affected before the correction still retain the values stored at that time. Because applying the correction changes dates on your boards, it is not applied automatically. Admins and board owners are asked to choose how the correction should be applied. 
 

1Select Fix timeline in the yellow banner at the top of the board. The banner appears on boards affected by the timeline rollup issue.

2Read the message in the Fix timeline dates pop-up, then select Continue. Recalculating corrects the affected parent item timelines and may shorten some of them. Nothing changes until you review the preview.

3Review the preview. Each affected item shows its current timeline, its adjusted timeline, and what it depends on. Select Export to Excel to save a backup, then select Resolve to apply the correction. Select Cancel to leave your dates as they are.

What each choice does:

If you’re unsure how to proceed and need further clarification, contact the support team at support@monday.com.

Dependency loops: circular dependencies are now blocked

What was possible before

It was possible to set items to depend on one another in a closed circle. In one scenario, item A was set to wait for item B while item B was set to wait for item A.

This could also happen between a parent item and its own subitems. A parent’s timeline is derived from its subitems, so if a subitem was also set to depend on its parent, each one was waiting for the other.

When a dependency circle exists, there is no valid order in which to calculate the timeline, and the items in the circle show incorrect dates. The items and dependencies themselves remain intact; only the calculated dates are affected.
 

What changed

Creating a dependency that would close a circle is now blocked, and a message explains why the dependency cannot be set. No action is required when creating new dependencies.

Existing boards

Where a dependency circle already exists, dependencies are not removed on your behalf. Each dependency in a circle may be a deliberate part of your plan, and removing the wrong one would change your schedule. The decision needs to be made by someone who knows how the work is planned.

Boards containing a dependency circle are flagged with a message when the board is opened. Follow these steps to review the loop and remove the dependency that does not belong:

1Select Review dependencies in the blue banner at the top of the board, then select Continue in the Resolve looped dependencies pop-up. The pop-up explains that tasks may end up referenced as dependencies in a way that creates a loop, and guides you through resolving it.

2Review the list of looping dependencies and select the X next to the one that does not belong. The suggested dependency is highlighted. Once the dependency that does not belong has been removed, the timeline recalculates automatically. No further action is needed.

If you are not certain which dependency to remove, contact the support team at support@monday.com.

Messages you may see in your account

You may see two in-product messages related to these changes. The first is a pop-up asking how the date correction should be applied, shown to admins and board owners on boards affected by the timeline rollup issue.

The second is a message flagging a dependency circle, which appears when a board containing a circle is opened, allowing the dependency to be reviewed and removed.

Both messages are expected. If you are unsure about a message you have received, contact the support team at support@monday.com.

FAQs

Was any data lost because of the dependency date issue?

No. No items, dates, or board history were removed at any point. The bug affected calculated values, not stored records.

Do I need to take action on boards or dependencies created after the date correction?

No. The bug is fixed and dependency loops are now blocked, so neither affects work created from this point onwards.

Why am I asked to choose how the dependency date correction is applied?

The correction changes dates on boards your team is actively working from, and only your team knows which outcome matches your plan. For dependency circles, each dependency may be intentional, so the decision about which to remove is yours.

Can the correction be reversed after it is applied?

No. Export the list of affected boards from the pop-up before continuing.

Could this have affected my automations?

It’s possible. A date-based automation or workflow that referenced an incorrectly calculated date may have run at a different time than intended.