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

(2) 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:

Business Process Flows

All responses (2)

Answers (0)

Suggested answer

w.p 1,614 on at

Like (0)

Report

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

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

Michael E. Gernaey 38,541 Super User 2025 Season 1 on at

Like (0)

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

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,

Community site session details

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

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

Markus Franz – Community Spotlight

Kudos to the March Top 10 Community Stars!

Leaderboard

Featured topics

Product updates

Community site session details

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

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

Markus Franz – Community Spotlight

Kudos to the March Top 10 Community Stars!

Subscribe to this forum!

Select categories

Leaderboard

Featured topics

Product updates