Logic Apps Management
  • 25 Sep 2020
  • 3 Minutes to read
  • Dark
  • PDF

Logic Apps Management

  • Dark
  • PDF

Article Summary

Associate a Logic App to a Serverless360 Composite Application to accomplish the following operations.

Enable/Disable Logic Apps

From Serverless360, you can:

  1. Enable/Disable a Logic App to reflect its status in the Azure Subscription.
  2. Initiate bulk operations - enable/disable multiple Logic Apps in a single click.

Run Trigger

Trigger the Logic App from the Serverless360. Put User Access Policy in place to restrict only authorized users to initiate a workflow execution.
Remote Actions

Quick Overview

Get a quick overview of all necessary information about the Logic App:

  • Definition
  • Status
  • Runs in last 24 hours
  • Integration Account if any
  • Plan
  • Trigger API Connection
  • Trigger frequency
  • Trigger Evaluation
  • Actions Count
    All the above-mentioned essential information is available in the Summary tab of the Logic App

Logic App Details View

View Logic Apps Properties

View properties of an Azure Logic App from Serverless360 itself

Success and Failure Run count

Based on color coding, you can know the Success and Failure Run counts instantly within the detail window of your Logic App.

Trigger and Run history

View all triggers to Logic App along with details about inputs and outputs of each trigger and the error reason in case of failure. If there are multiple triggers, the trigger history can be filtered by the trigger, as in Azure Portal.
It is possible to drill down to every run action to understand the work flow execution. Say for example consider a Logic App with a trigger 'when a new message arrives in the Service Bus Queue'. The requirement is to identify which Service Bus message has been processed in a specific trigger or run action. The message Id of the processed message can be tracked in the trigger or run action detail. Below is an illustration of the same
Run history & trigger history

Resubmitting Runs

A Logic App run would fail due to failure in one of its actions and it occurs quite often in a business orchestration. Serverless360 already facilitates viewing the run history and accessing the details of the failed runs.
As a value add to enhance Logic Apps management, Serverless360 now brings in the capability to Resubmit the runs from the Run History.
Though run resubmission is possible in Azure portal, the challenge is lack of clarity in identifying the resubmitted runs. Serverless360 overcomes this challenge by adding a 'Resubmission of actual run' tag to those runs which are resubmitted either from Serverless360 or from Azure Portal.
Clicking the “Resubmission of actual run” tag will fetch the details of the actual parent run.
A tag 'Resubmitted' will be added to the actual parent run. Clicking the "Resubmitted" tag will fetch the list of child runs.
Resubmission of logic App

In addition to resubmitting the runs, a tag 'Ignore' can be associated with a run along with the description. This ignore tag is visible only in Serverless360, will not have any impact on the actual runs.

Ignore runs

Serverless360 will not recognise the correlation between the actual and resubmitted runs, if a custom Correlation Id is used in the Workflow.

Filter Run History

Serverless360 now enables filtering run history. Search for a specific run by its 'Identifier'. It is also possible to filter the run history by 'From Date' and 'To Date' along with the 'Status' of the run.

Filter using search


Operations like Enable/ Disable or Delete that changes the state of the associated Logic App can be tracked using Serverless360. Put User Access Policy in place and permit only authorized users to modify state of the Logic App only through Serverless360. This way ensure every user action on the Log App being tracked in Serverless360 Governance and Audit.

We'd love to hear your thoughts
Please visit our feedback system to suggest new Features or Enhancements. You can also take a look at our Roadmap

Was this article helpful?