Check Flow Connector Error

Original post is here.

There is a thing that many people feel using Microsoft Flow, connection of the created connector becomes a connection error periodically. Because it is due to the expiration of the access token used at the time of connection, it may be an error, but checking from the portal every time was troublesome.

I tried to automate this check with Flow this time.

Since it is quite long as an entry, those who want to check in advance have prepared packages exported to github, so please use here as well.

Workflow Function can not be used with LogicFlow's Trigger

Original post is here.

There are some triggers that can be used in LogicFlow that can be set variously. In many cases, direct value is set in most cases, but in some cases you may want to use the function of LogicFlow. However, it was inconvenienced by current specifications.

Like PIVOT conversion of JSON value

Original post is here.

JSON with arrays is troublesome in getting values when operating with LogicApps / Flow. Converting the values horizontally and vertically like PIVOT and converting so that related values can be acquired with specific key values may make subsequent processing easier.

For example in this case. Normally, you loop through SampleArray and check the values one by one. Since the current Logic Apps and Flow can only deal with this way, the purpose is to want to make it even easier here.

Delete approval by Flow Management for Admin connector

Original post is here.

Recently Flow Management for Admin connector has been added. Compared with the conventional management connector, the action of the management system has become more increased. Among them, there was an action called Remove Approval, so I checked what kind of movement it would take.

Try-Catch-Finally Patter in LogicApps/Flow

Original Post is here.

In Logic Apps and Flow, patterns for error handling are available. For those who write the program, it is a familiar Try-Catch-Finally format.

Acquire execution history of LogicApps with LogicApps

Original post is here.

I attempted to retrieve the execution history of Logic Apps and tried to see if I could see the date and time that I processed recently.

Respond to processing that requires long time with Logic Apps / Flow

Original Post is here.

I got a question from my friend "Logic Apps timeout 120 seconds, I want to avoid somehow", so it seemed interesting and tried it

Template Logic Apps including API connection

ORiginal Post is here.

Although I was doing various templates to distribute Logic Apps including API connection, I tried collecting it as a memorandum because I took a lot of trouble in rewriting the point and Template when distributing it.

This entry was made with reference to Sacha Bruttin 's wonderful entry. Deploy Logic Apps & API Connection with ARM https://www.bruttin.com/2017/06/13/deploy-logic-app-with-arm.html

Create Passwords using LogicFlow

Original Post is here.

For some reason I created LogicFlow to register accounts. However, there was a problem of what to do with the initial password. Although it seems likely to go easy without using Azure Functions, I decided to do it with Logic Apps.

How to change to a new Logic Apps IF connector

In the past update, the IF connector of Logic Apps was updated and it was easy to describe it even in a newly nested state. There was a mistranslation of Japanese, but it is very easy to deal with multiple judgment conditions. However, unlike conventional IF connectors, the description method is not automatically updated. In order to update this, we need to change the description directly in CodeView, so summarize the rewriting method.

Auth error is returned depending on the value of RowKey(Table Storage Connector)

Original post is here.

EventGrid trigger raises Error

Original post is here.

I am making various LogicFlow using EventGrid. The EventGrid trigger may become an error the other day, and I am very troubled and I will keep that correspondence.

Rewrite child element value using setPropety Function.

Original post is here.

It is a setProperty function for manipulating the value of a JSON object in LogicFlow, but if you wanted to rewrite a child element, it took a bit of effort to do it.

Error handling in LogicFlow

Original post is here.

Error handling is not limited to LogicFlow in most cases. Even if you do not need to do anything when an error occurs, you need to know that an error occurred. I tried summarizing what correspondence can be taken with LogicFlow.

The error handling that can be implemented in LogicFlow is the following pattern.

• Setting the action with the execution condition set to "Error"
• Monitor with Action Failed specified by alert rule

1: Setting action to be executed on error

The actions used in LogicFlow can set execution conditions. It can be specified by combining four types of "Successful", "When Failed", "Skipped", "Time Out", and when performing error handling, "Including When Failed" will be included.

Since this execution condition is judged against the immediately preceding action, if an error occurs somewhere in the processing, it can not be used as it is as it is. In such a case, it is necessary to combine multiple actions into one action using "scope".

Since this execution condition is judged against the immediately preceding action, if an error occurs somewhere in the processing, it can not be used as it is as it is. In such a case, it is necessary to combine multiple actions into one action using "scope".

When there are cases where it is not executed at the same time, such as normal time, error occurrence, etc., I think that it is one thing to divide it as parallel processing.

In summary, this method is suitable for use when "some processing is required at the same time when an error occurs". Is it a case where it is somewhat necessary to handle some action on one action rather than simply outputting logs.

2: Specify Action Failed with Alert Rule

Another way, error handling is slightly different nuance. It is limited to LogicApps, but it has a function of issuing an alert when it matches the condition specified as Azure's function, and it is a method using it.

After selecting the alert rule, click Add metric alert.

We will set conditions to generate alerts.

The condition is "metric" "condition" "threshold". If you specify Action Failed here, you can generate an alert in "When some action fails".

For details on what to do if an alert occurs, use "Webhook" at the bottom of the screen or "Execute action". It is possible to call a specific API when an alert occurs on Webhook, or call a specific LogicApps by executing an action.

I will attach the captured sample as to what kind of data actually flows.

In this context, Japanese is described as "しっぱいしました" as a Description, but what is described in the "Description" column of the alert rule will be cooperated as it is. The value of Condition is also set in accordance with the condition of the alert rule. Therefore, it can not be used to grasp detailed error contents. It is possible until LogicApps detects that some error has occurred.

In summary, the error handling in the alert rule is "to detect whether an error occurred in one LogicApps", it is not a detailed error response, and it is larger than the previous execution condition such as recovering throughout I think that it is suitable for correspondence.