I’m encountering an issue with automations on my project boards. When I make changes to an automation from my windows laptop, some of the updates don’t immediately appear when I access the same board on another device or browser. For example, I update a status-change automation, but the board seems to follow the previous workflow until a refresh.
Here’s what I’ve tried so far:
Clearing browser cache and cookies
Logging out and back in
Testing on different browsers
Checking automation logs for any indications
Questions:
Has anyone experienced automations syncing with a slight delay across devices?
Could this be related to caching or backend sync timing?
Are there recommended ways to ensure updates propagate quickly?
Any guidance or tips would be greatly appreciated. Thanks in advance!
Sometimes there is a short lag between updates. To your questions:
1. Delay across devices
Yes, there can be a slight delay (usually a few seconds, occasionally longer) before automation changes fully propagate. Things that can make it more noticeable:
Having the same board open on multiple tabs/devices at once
Editing the automation in one place while another session is “stale” and hasn’t refreshed its state
Heavy automation load on the account/board (lots of rules firing frequently)
The board will often appear to follow the “old” workflow until that session updates its internal state or you manually refresh.
2. Caching vs backend sync
It’s a bit of both:
Frontend/UI caching / stale session
Each open browser tab has its own local state. If you change an automation in Tab A (laptop) and Tab B (another device) is still running, Tab B might keep “thinking” in terms of the old automation until it refreshes or receives an update signal.
Backend propagation
Automation changes are stored server-side; there can be a brief period where the UI shows the new rule, but execution might still be catching up, especially under load. This is usually short, but it can produce exactly what you described—seeing old behavior until refresh.
3. Ways to ensure faster / reliable propagation
These practices help reduce confusion:
Refresh any other open sessions after editing automations
After saving changes to an automation, reload the board on other browsers/devices before testing.
If you use the desktop app and browser together, refresh both.
Avoid editing from multiple places simultaneously
Try to do automation edits from one device/browser at a time.
Close duplicate board tabs when you’re actively changing recipes.
Use the Automation Activity Log to confirm which recipe ran
After a status change, check the board’s Automation Activity to see which version of the automation executed (name, conditions, time).
This tells you whether the backend is using the new logic or still the old one.
Give it a short buffer before testing complex changes
For accounts with many automations, wait ~10–20 seconds after saving a big change before triggering tests on other devices.
Check for app vs browser differences
If you’re using the Windows desktop app in addition to browsers, make sure the app is fully updated, and force a refresh (Ctrl+R) after automation edits.
If you’re seeing delays longer than ~30–60 seconds after a refresh, or the automation logs show the oldlogic firing even though you’ve saved changes, that can indicate a real issue. In that case, I’d:
Capture:
Board name + URL
Automation screenshot (before and after change)
A screenshot of the Automation Activity log showing the “wrong” behavior
Send those to monday.com support so they can check for a backend sync problem on your account.
If you share a specific automation example (trigger + condition + action) and how you changed it, I can suggest a more targeted test flow to verify the behavior across devices.