I’m trying to set up a automation so that when the status of a task is set to done, a notification is sent to all of the users that are assigned to that task.
I’ve managed to get halfway there, but when the automation goes, it ends up sending a notification PER TASK that’s already completed, rather than a single notification for the task where the status changed.
We have six states for the statuses and the flow of the states aren’t necessarily sequential. Having a button to cycle through will lessen the user experience most likely.
Do you mean within the content? Isn’t that just what’s displayed in the notification they get? It shouldn’t affect the number of notifications received.
I assume the problem is somewhere in the automation code (in the section then), but it could very well be the way you update the row(s) in the first place. If you update the row(s) with a button, perhaps you are updating a lot of rows?
You really have to share a (dummy) doc with the community or invite someone (like me) to look at your real doc in order to figure out what is going on. A screen print does not provide enough information, so it becomes just guessing.