@Simswati ,
This are just some thoughts ...
Actually I'm afraid that is a little bit tricky if your data source is Sharepoint, because there is no way to control what column change generate the trigger in Sharepoint.
You can control the trigger start based on a column value, like @SudeepGhatakNZ suggested, but the flow will trigger every time you change any columns values and the calculated column has 'Due for review' as value.
What I suggest is to have a supplementary column to keep under control the unwanted flow runs.
Main flow:
Trigger with the trigger condition set to:
@and(equals(triggerBody()?['calculatedColumn'],'Due for review'),equals(triggerBody()?['runAllowed'],'true'))
Action to send email
Action to update the current item - runAllowed column - with 'false'
Secondary flow:
Trigger with the trigger condition set to:
@and(not(equals(triggerBody()?['calculatedColumn'],'Due for review')),equals(triggerBody()?['runAllowed'],'false'))
Action to update the current item - runAllowed column - with 'true'
Hope it helps !
