1

The problem was caused by UserId being null in several elements of the data received from the HTTP Get, while that is set as required in the JSON Schema... initially we solved it by using the below in the HTTP Get: _api/web/sitegroups/getbyname('Legal Owners')/users?$filter=UserId+ne+null Then we were given a better and more elegant solution on the Power ...


1

Try removing UserId from the 'required' array at the end of your JSON schema. Any values specified in that array must be present with every return/trigger, or the Flow will fail. If 'Email' is the only value you truly need, I would make that the only required value. Like this: "required": [ "Email" ]


1

here is short version: Create Flow with Recurrence Get Files from Library (if there will be more libraries, there should be more these functions. I selected my test site and default Documents library. I also filtered documents only for new (created 7 days ago and newer) You can change this. Created gt '@{getPastTime(7, 'Day', 'o' )}' Add foreach loop - ...


1

You won't be able to use a Flow to query or terminate another Flow You'll instead need to drive your Flow by using informative custom columns in your affected list or library - for example, "Workflow Status" - and build conditions in your Flow that inspect these values to determine whether to proceed or not. For example, we could setup a list with a ...


Only top voted, non community-wiki answers of a minimum length are eligible