Teams message sent 1 hour before a date is reached in a sharepoint list

(1) Share

Report

Posted on by CL-04042223-0

Hello, I am creating a flow to send a message in teams 1 hour before a date is reached in a Sharepoint list. I created a the following flow which works, however if the sharepoint item is modified after being created, there is a duplicate run/message sent in teams. Is there a way around this? We need the modified items to still send a reminder with the new date.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,978 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi @CL-04042223-0

Hopefully I can help. However, I am confused about this statement:

Hello, I am creating a flow to send a message in teams 1 hour before a date is reached in a Sharepoint list. I created a the following flow which works

I do not see how this does what you said. You are using an Automated Flow, so how exactly does this flow ensure that you send a message 1 hour before any date you have stored somewhere as it only fires when a file is created or modified, what if it isn't?

Can you please clarify the gap.

Then you said

However, if the SharePoint item is modified after being created, there is a duplicate run/message sent in teams. Is there a way around this? We need the modified items to still send a reminder with the new date.

Again there is a gap, what new date?

The question you are asking is a business process question, not really a technical one and I am going to hypothesis as I don't have the answers to the questions or details, just based on decades of experience,

1. You have a Date, whatever it is already configured, lets call it 4/1/12:00 PM

2. Something triggers a file to be created or modified so that it does in fact happen within that 1 hour (otherwise I do not understand)

3. Now 5 minutes later, someone modifies the file (for the first time or again) but the issue is, its still within the 1 hour, but you already sent a notification and you said you don't want to send more than 1 within that 4/1/212:00 PM

From a business perspective, do you skip the notification and ignore the update or not? That's for you to determine

4. I assume at some point, maybe at 4/1/11:59 you update the time to another time period that documents have to be notified on with an hour say 4/1/5:00 PM

Are you expecting, in my example, the notification that got skipped as it would have caused a duplicate at the 4/1/ 12:00 PM time, to "now" happen even though there is no event to trigger making that happen, no mapping or tracking etc?

These are business decisions of what the process should look like, then comes the architecture part.

Please read this over, and please describe your business process and needs fully as the technology is irrelevant to that

Cheers,

Was this reply helpful? Yes No
Suggested answer

w.p 8,345 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Will changing the trigger to "When an item is created" fix the issue?

Was this reply helpful? Yes No
CL-04042223-0 2 on at

Like (0)

Report
Copy link

Link copied!

Thank you for all the responses.

Process/Goal:

1. Enter an item into the sharepoint list (calendar) with a "go live" date (example April 1, 2025 at 9am)

2. Teams message at April 1, 2025 at 8am with the name of the item on the sharepoint list and tags the user who created the entry

The current flow (which sends duplicates):

1. When an Item is Created or Modified in the list

2. Removing anything in the recycle bin (that was created on accident and deleted)

3. Check if the date is in the past, if NO:

4. Compose a teams message

5. Delay message until 1 hour before the date (April 1, 2025 at 8am)

6. Post in channel

If someone modifies the date, the sharepoint list item will trigger another flow and send a duplicate message (one with the original date, and one with the new date). However if we only set it up to send a message when the date is created, we miss any edits or changes to the date.

Was this reply helpful? Yes No
Suggested answer

David_MA 14,499 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
You need to do this differently, but it will be difficult with your requirement of needing to send the reminder one hour before. This may work:

Create a scheduled flow that runs every hour.

Use a get items action with a filter query to get the items where a reminder needs to go in the next hour (flow runs at noon, it gets items that need to go out from 13:00 to 13:59).

Use an apply to each to process each item found to send the reminder.

Then the best way to handle sending the reminder would be to create a child flow where you would pass the date/time the reminder needs to be sent, and the ID of the list item to the child flow.

In the child flow, reply back to the parent flow so it moves on to the next item in the apply to each, and then add a delay in the child flow to when the reminder needs to be sent. When the delay ends, use the ID sent to the child flow in a Get item action to get the details needed for the Teams message.

If the flow finds five items, it will create five runs of the child flow.

Was this reply helpful? Yes No