Issue with Power Flow to output recurrent email based on certain conditions

[JMVE10]

I keep having issues with my Power Flow code it either runs but doesn't work or I'm not able to create it due to certain restrictions. 

I would like to create a recurrent email reminder to a specific person daily if there is a type of request A in the form that meets conditions B and C. They could already be logged in the system as request type A or any new request that meets request type A will generate a daily email to a person if conditions B and C are met.

The request type A data is pulled from a SharePoint Site and specific List. I tried but options with "When an item is created or modified" and with "Get item" and still unable to successfully run the code.

Any help would be appreciated. 

Thanks!

[Andrew_J]

@JMVE10 

I need to reconfirm what you want:

In a SharePoint List there is an item with something that means a request type A is required, say a spillgage on the floor requires a cleaner to come and remove the spillage.  But from what you have said request type A is also dependent on condtions B and C, so the spillage on the floor could contain oil and water.  So the cleaner should come with relvant items to clean the oil and water from the floor.

From my logic if B and C need to input into request A then surly B and or C should be the driver for the flow.  I assume your SP List has

Request A	Condtion B	Condition C

To build the flow requires clarity, and I think there is none at the moment as what will the trigger be, so I can see your predicament.

Regards

Andrew

with request type A,

data is pulled from a SharePoint List,

[JMVE10]

Hello Andrew,

So I have a Form that gets filled out with certain information. The request type is A, and the request status is B. We currently have mutliple requests with request type A and request status B already in the system. I would like to generate a Power Flow that sends a daily email to a specific person every time a request type A is submitted, but if the Condition is request status B that person will be getting daily email reminders on that specific item until it changes to request status C. Once it changes to request status C it means the task has been completed so no more email reminders are required.

[Andrew_J]

@JMVE10 

Okay this sounds like a construction issue, and commenting on a submission of a drawing or documents.  We work from C to A but I can help you with A to C as you want. 

However there is still confusion in my mind between the request type A and B.  And in your post above we have a condtion type B then we have a Condtion type C.  

So if we can clear up the confusion we can start on the flow which may need you to change your list.  Maybe you writing this out and spending time on it will help you get over the confusion that I am seeing.  It may help with you being able to look at the issue of the flow.

Regards

Andrew

[jaaronanderson]

make a dedicated job account like

"servicejobprocessor@domain.tld"

then simply push to an inbox a copy of each for evaluation and leverage inbox rule conditionals ...

then choose to retain original inbound copy for business continuity if/when end personnel turns over ...

just file it away in a nested deep graveyard folder

[jaaronanderson]

on task C make a dedicated flow action job sceduled to evaluate a list or column that user who gets email takes an action on to complete a manual form or approval in teams (i like) if completed sets the recod column to true and doesnt kick off a new email reminder scans on to next row till next false no break in job..