- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 11:33 AM
Hi All,
If you see the picture the record has two fields review date and status . Currently status is "in use" when review date is ahead of current date but status will be "retire" immediately when review date passes . Can we achieve it through flow designer ? Actually scheduled jobs are making the system slow so trying to achieve it through flow. In this picture when review date passes on 8th may the status will automatically updated to retire on the fly.
Thank you
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 01:29 PM - edited 05-06-2025 01:31 PM
1. Trigger type is scheduled, daily.
2. First action is Look up Records (plural) where Review Date is Yesterday.
3. For each item loop.
4. Update Record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 01:31 PM
Is there any script to write?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 02:38 PM
No, this should be a no code solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 12:13 PM
I tried this logic but it updated all the records which have state new to cancel irrespective of day (yesterday). But I want it should only those records which have due date on previous day of current day .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:20 AM - edited 05-07-2025 11:24 AM
What will be logic here to measure due date is passed from current date ? Couldn't find the option retired on yesterday .

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:37 AM
I'm not sure the original record is even on the incident table. I was using Knowledge as an example