Usage
The command can look like this:
m365 flow run trigger get --environment --flow --name
or it will be updated the m365 flow run get command.
Description
I am of the opinion that the command "flow run get" does not currently have enough information about the specified flow run. For example the trigger output would give me more information about the flow run. This information you can get from the body of the res.properties.trigger.outputsLink.uri. In addition the command also output the flow run url.
Options
-e, --environment <environment> | The name of the environment where the flow is located
-f, --flow <flow> | The name of the Power Automate flow for which to retrieve information
-n, --name <name> | The name of the run to get information about
| Option |
Description |
-o, --option <option> |
option |
-o, --output [output] |
Output type. json,text. Default text |
--verbose |
Runs command with verbose logging |
--debug |
Runs command with debug logging |
Additional Information
In my way i use this code to get more informations about the flow run.
So my output is this:
In this way I get an assignment from a flow run to its specific SharePoint itm, which triggered the flow. This helps me test a flow with multiple test data and find a reported bug that the flow has encountered on a SharePoint item.
Usage
The command can look like this:
m365 flow run trigger get --environment --flow --nameor it will be updated the
m365 flow run getcommand.Description
I am of the opinion that the command "flow run get" does not currently have enough information about the specified flow run. For example the trigger output would give me more information about the flow run. This information you can get from the body of the res.properties.trigger.outputsLink.uri. In addition the command also output the flow run url.
Options
-o, --option <option>-o, --output [output]json,text. Defaulttext--verbose--debugAdditional Information
In my way i use this code to get more informations about the flow run.
So my output is this:
In this way I get an assignment from a flow run to its specific SharePoint itm, which triggered the flow. This helps me test a flow with multiple test data and find a reported bug that the flow has encountered on a SharePoint item.