Logic Apps for visual workflows in Azure - Step-by-Step Execution

Process Flow - Logic Apps for visual workflows

Start Logic App Trigger

↓

Evaluate Trigger Condition

↓

Run Actions

↓

Check Action Results

↓

End or Loop/Retry

Logic Apps start with a trigger, then run actions if conditions are met, and finally end or wait for the next trigger.

Execution Sample

Azure

Trigger: When HTTP request received
Action 1: Get file content
Action 2: Send email with file
Condition: If file exists
End

This Logic App waits for an HTTP request, then gets a file and sends it by email if the file exists.

Process Table

Step	Action	Input	Condition Check	Result	Next Step
1	Trigger fires	HTTP request received	N/A	Trigger activated	Run Action 1
2	Get file content	File path from trigger	N/A	File content retrieved	Check if file exists
3	Condition check	File content	File exists?	Yes	Run Action 2
4	Send email	File content	N/A	Email sent	End Logic App
5	End	N/A	N/A	Workflow complete	Wait for next trigger

💡 Logic App ends after sending email and waits for the next trigger.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
TriggerStatus	Not fired	Fired	Fired	Fired
FileContent	Empty	Loaded	Loaded	Loaded
ConditionResult	Unknown	Unknown	True	True
EmailStatus	Not sent	Not sent	Not sent	Sent

Key Moments - 2 Insights

Why does the Logic App wait after the trigger if the condition is not met?

Because as shown in step 3 of the execution_table, if the condition 'File exists?' is No, the Logic App does not run the email action and waits for the next trigger.

What happens if the trigger never fires?

The Logic App stays idle and does not run any actions, as the trigger is the starting point (step 1). No further steps execute without it.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after Step 2?

A File content retrieved

B Trigger activated

C Email sent

D Workflow complete

💡 Hint

Check the 'Result' column for Step 2 in the execution_table.

At which step does the Logic App check if the file exists?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Condition Check' column in the execution_table.

If the file does not exist, what happens next according to the execution flow?

A Send email anyway

B End Logic App immediately

C Wait for next trigger without sending email

D Retry getting file content

💡 Hint

Refer to the concept_flow and step 3 in the execution_table where condition is checked.

Concept Snapshot

Logic Apps start with a trigger that listens for events.
They run actions in order, based on conditions.
Conditions decide if next actions run or wait.
Workflows end or wait for next trigger.
Visual design helps build and understand flow.

Full Transcript

Logic Apps are visual workflows in Azure that start when a trigger event happens, like receiving an HTTP request. Once triggered, the Logic App runs actions step-by-step. For example, it can get file content and then check if the file exists. If the file exists, it sends an email with the file. If not, it waits for the next trigger without sending the email. Variables like TriggerStatus and FileContent change as the workflow runs. This flow helps automate tasks without writing code, using a clear visual design.

Practice

1. What is the primary purpose of Azure Logic Apps in cloud workflows?

easy

A. To create automated workflows visually without writing code

B. To manually manage virtual machines

C. To store large amounts of data

D. To write complex backend applications

Solution

1. Step 1: Understand Logic Apps purpose

   Logic Apps are designed to automate workflows visually, making it easy to connect services without coding.

2. Step 2: Compare options

   Options B, C, and D describe other Azure services or tasks unrelated to Logic Apps' main function.

3. Final Answer:

   To create automated workflows visually without writing code -> Option A

4. Quick Check:

   Logic Apps = Visual automation [OK]

Hint: Logic Apps automate visually, no code needed [OK]

Common Mistakes:

• Confusing Logic Apps with data storage services
• Thinking Logic Apps manage virtual machines
• Assuming Logic Apps require coding

2. Which of the following is the correct way to start a Logic App workflow?

easy

A. By creating a virtual machine

B. By writing a function in C#

C. By defining a trigger that listens for an event

D. By uploading a database file

Solution

1. Step 1: Identify how Logic Apps start

   Logic Apps begin with a trigger that waits for an event or condition to start the workflow.

2. Step 2: Eliminate incorrect options

   Options B, C, and D are unrelated to Logic Apps workflow initiation.

3. Final Answer:

   By defining a trigger that listens for an event -> Option C

4. Quick Check:

   Logic Apps start with triggers [OK]

Hint: Logic Apps always start with a trigger [OK]

Common Mistakes:

• Thinking code is needed to start Logic Apps
• Confusing Logic Apps with VM or database setup
• Ignoring the trigger concept

3. Consider a Logic App with a trigger on receiving an email and an action to save attachments to OneDrive. What happens when an email with two attachments arrives?

medium

A. Only the first attachment is saved, the second is ignored

B. Attachments are deleted from the email

C. The Logic App fails with an error

D. Both attachments are saved to OneDrive automatically

Solution

1. Step 1: Understand the trigger and action

   The trigger activates on email receipt; the action processes all attachments.

2. Step 2: Analyze behavior with multiple attachments

   Logic Apps handle each attachment, saving both to OneDrive automatically.

3. Final Answer:

   Both attachments are saved to OneDrive automatically -> Option D

4. Quick Check:

   Multiple attachments = all saved [OK]

Hint: Logic Apps process all items in a trigger event [OK]

Common Mistakes:

• Assuming only one attachment is processed
• Expecting failure on multiple attachments
• Thinking attachments get deleted automatically

4. You created a Logic App with a trigger on HTTP request and an action to send an email. The email is never sent after calling the HTTP endpoint. What is the most likely issue?

medium

A. The HTTP trigger URL was not copied correctly

B. The email action is missing a recipient address

C. The Logic App is not connected to a virtual network

D. The Logic App requires a database connection

Solution

1. Step 1: Check trigger and action setup

   The HTTP trigger activates the workflow; the email action must have a recipient to send mail.

2. Step 2: Identify missing email recipient

   If the recipient is missing, the email action silently fails or does not send.

3. Final Answer:

   The email action is missing a recipient address -> Option B

4. Quick Check:

   Email action needs recipient [OK]

Hint: Always set email recipient in Logic Apps [OK]

Common Mistakes:

• Assuming trigger URL copy error causes no email
• Thinking virtual network is required for email
• Believing database connection is needed

5. You want to build a Logic App that triggers when a file is added to an FTP server, then copies the file to Azure Blob Storage, but only if the file size is less than 5 MB. How should you design this workflow?

hard

A. Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true

B. Use a Blob Storage trigger and copy files to FTP server

C. Use an FTP trigger and copy all files to Blob Storage without conditions

D. Use a manual trigger and upload files to Blob Storage

Solution

1. Step 1: Select correct trigger

   The workflow must start when a file is added to FTP, so use an FTP trigger.

2. Step 2: Add condition to check file size

   Insert a condition action to verify if the file size is less than 5 MB before copying.

3. Step 3: Copy file to Blob Storage if condition met

   If the condition is true, perform the copy action to Azure Blob Storage.

4. Final Answer:

   Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true -> Option A

5. Quick Check:

   Trigger + condition + action = correct design [OK]

Hint: Use condition to filter files before action [OK]

Common Mistakes:

• Using wrong trigger type
• Skipping file size condition
• Copying files without filtering
• Using manual trigger instead of automatic