Functions with queue triggers in Azure - Step-by-Step Execution

Process Flow - Functions with queue triggers

Message added to Queue

↓

Queue Trigger detects message

↓

Function starts executing

↓

Function processes message

↓

Function completes successfully

↓

Message removed from Queue

↓

Wait for next message

When a message is added to the queue, the queue trigger detects it and starts the function. The function processes the message and then the message is removed from the queue.

Execution Sample

Azure

public static void Run([QueueTrigger("myqueue-items")] string myQueueItem, ILogger log)
{
    log.LogInformation($"Processing message: {myQueueItem}");
}

This Azure Function triggers when a new message arrives in 'myqueue-items' queue and logs the message content.

Process Table

Step	Queue State	Trigger Detection	Function Execution	Message State
1	Queue: ["msg1"]	Detects 'msg1'	Starts processing 'msg1'	Message 'msg1' locked for processing
2	Queue: ["msg1"]	No new message detected	Processing 'msg1' continues	Message 'msg1' locked
3	Queue: []	No new message detected	Function completes successfully	Message 'msg1' removed from queue
4	Queue: []	Waiting for new messages	Idle	No messages

💡 Function stops after processing and removing the message; waits for new messages.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Queue Messages	["msg1"]	["msg1"]	["msg1"]	[]	[]
Function State	Idle	Running	Running	Completed	Idle
Message Lock	None	Locked	Locked	Removed	None

Key Moments - 2 Insights

Why does the message stay in the queue during processing?

The message is locked during processing to prevent other functions from processing it simultaneously, as shown in execution_table rows 1 and 2.

What happens if the function fails during processing?

If the function fails, the message remains in the queue unlocked or becomes visible again for retry, but this example shows successful completion in row 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the function state at step 2?

A Idle

B Completed

C Running

D Waiting

💡 Hint

Check the 'Function Execution' column at step 2 in the execution_table.

At which step is the message removed from the queue?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Message State' column to see when the message is removed.

If a new message 'msg2' arrives after step 4, what will the queue state be?

A Queue: []

B Queue: ["msg2"]

C Queue: ["msg1", "msg2"]

D Queue: ["msg1"]

💡 Hint

Refer to the 'Queue Messages' variable in variable_tracker after new messages arrive.

Concept Snapshot

Azure Functions with queue triggers run automatically when a new message arrives in a storage queue.
The function locks the message during processing to avoid duplicates.
After successful processing, the message is removed from the queue.
If processing fails, the message remains for retry.
This enables event-driven, scalable background processing.

Full Transcript

When a message is added to an Azure Storage Queue, the queue trigger detects it and starts the Azure Function. The function locks the message to prevent other instances from processing it simultaneously. The function processes the message and upon successful completion, the message is removed from the queue. The function then waits for new messages to arrive. If the function fails, the message remains in the queue for retry. This process allows automatic, scalable background processing triggered by queue messages.

Practice

1. What does an Azure Function with a queue trigger do when a new message arrives in the queue?

easy

A. It automatically starts and processes the message.

B. It waits for manual activation to process the message.

C. It deletes the message without processing.

D. It sends an email notification only.

Solution

1. Step 1: Understand queue trigger behavior

   Queue triggers start the function automatically when a new message arrives in the queue.

2. Step 2: Identify the function's action

   The function processes the message as soon as it triggers without manual intervention.

3. Final Answer:

   It automatically starts and processes the message. -> Option A

4. Quick Check:

   Queue trigger = automatic start [OK]

Hint: Queue triggers start functions automatically on new messages [OK]

Common Mistakes:

• Thinking the function needs manual start
• Assuming the message is deleted without processing
• Confusing triggers with notifications

2. Which of the following is the correct way to declare a queue trigger in an Azure Function using Python?

easy

A. @app.queue_trigger(arg_name='msg', queue_name='myqueue', connection='AzureWebJobsStorage')

B. @blob_trigger(container_name='mycontainer')

C. @http_trigger(methods=['GET'])

D. @timer_trigger(schedule='0 */5 * * * *')

Solution

1. Step 1: Identify the correct trigger decorator

   Queue triggers use @app.queue_trigger with queue_name, connection, and arg_name parameters.

2. Step 2: Check other options

   Blob, HTTP, and timer triggers use different decorators and parameters.

3. Final Answer:

   @app.queue_trigger(arg_name='msg', queue_name='myqueue', connection='AzureWebJobsStorage') -> Option A

4. Quick Check:

   Queue trigger decorator = @app.queue_trigger [OK]

Hint: Queue triggers use @app.queue_trigger decorator with queue_name [OK]

Common Mistakes:

• Using wrong trigger decorators like @blob_trigger
• Missing required parameters like queue_name
• Confusing connection string names

3. Given this Azure Function code snippet in Python, what will be printed when a message with content 'Hello' arrives in the queue?

import logging
import azure.functions as func

def main(msg: func.QueueMessage):
    message = msg.get_body().decode('utf-8')
    logging.info(f'Received message: {message}')

medium

A. Error: msg.get_body() is not a function

B. Received message: b'Hello'

C. No output because logging is disabled

D. Received message: Hello

Solution

1. Step 1: Decode the message body

   The message body is decoded from bytes to string using decode('utf-8'), so 'Hello' is a string.

2. Step 2: Logging output

   The logging.info call prints 'Received message: Hello' to the logs.

3. Final Answer:

   Received message: Hello -> Option D

4. Quick Check:

   Decoded message logged = 'Received message: Hello' [OK]

Hint: Decode bytes to string before logging message content [OK]

Common Mistakes:

• Logging raw bytes without decoding
• Assuming get_body() is not callable
• Thinking logging is off by default

4. You deployed an Azure Function with a queue trigger, but it never runs when messages arrive. Which of these is the most likely cause?

medium

A. The function code has a syntax error in the main function.

B. The connection string for the storage account is incorrect or missing.

C. The queue name is misspelled in the trigger configuration.

D. The function app is set to manual scale mode.

Solution

1. Step 1: Check connection string

   If the connection string to the storage account is wrong or missing, the function cannot listen to the queue.

2. Step 2: Consider other causes

   While syntax errors cause deployment failure, misspelled queue names cause no trigger, but connection issues are most common.

3. Final Answer:

   The connection string for the storage account is incorrect or missing. -> Option B

4. Quick Check:

   Connection string error = no trigger run [OK]

Hint: Verify storage connection string first if function doesn't trigger [OK]

Common Mistakes:

• Ignoring connection string errors
• Assuming scaling mode stops triggers
• Overlooking queue name spelling

5. You want to process messages from two different queues in the same Azure Function app. What is the best way to configure this?

hard

A. Use one function with two queue triggers on the same method.

B. Combine both queues into one and use a single queue trigger.

C. Create two separate functions within the app, each with its own queue trigger for each queue.

D. Use a timer trigger to poll both queues manually.

Solution

1. Step 1: Understand function triggers

   Each function can have one trigger. To listen to two queues, create two functions with separate queue triggers.

2. Step 2: Evaluate other options

   One function cannot have two queue triggers on the same method; combining queues may not be feasible; timer triggers require manual polling.

3. Final Answer:

   Create two separate functions within the app, each with its own queue trigger for each queue. -> Option C

4. Quick Check:

   One trigger per function = two functions for two queues [OK]

Hint: Use separate functions for each queue trigger [OK]

Common Mistakes:

• Trying multiple triggers on one function method
• Merging queues without control
• Using timer triggers instead of queue triggers