---
title: "Run message"
slug: "run-message"
description: "Run messages efficiently with customizable source and target connectors, and set up data synchronization for batch processing in Connectivity Studio."
tags: ["Task topic"]
updated: 2026-07-15T08:34:20Z
published: 2026-07-15T08:34:20Z
canonical: "docs.staedean.com/run-message"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run message

You can run a message directly. You can do so, for example, for testing purposes or to run a specific message in batch.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. On the **Message** tab, in the list, find and select the desired message.
3. Click **Run**.
4. Each message has a source connector defined. You can overrule the message source connector by defining a different source connector when you run the message.

In the **Source connector** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> The type of connector you can define depends on the type of the message source connector.
> 
> For the following message source connector types, the message run source connector type must be the same:
> 
> - **Azure file storage**
> - **Direct SQL**
> - **Staging journal**
> - **Database**
> - **D365 F&SCM**
> 
> For the following message source connector types, you can use any of these types as the message run source connector:
> 
> - **Upload and download**
> - **SharePoint**
> - **Azure Blob Storage**
> - **Service Bus queue**
> - **Web service**
5. Each message has a target connector defined. You can overrule the message target connector by defining a different target connector when you run the message.

In the **Target connector** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> The type of connector you can define depends on the type of the message target connector.
> 
> For the following message target connector types, the message run target connector type must be the same:
> 
> - **Azure file storage**
> - **Direct SQL**
> - **Staging journal**
> - **Database**
> - **D365 F&SCM**
> 
> For the following message target connector types, you can use any of these types as the message run target connector:
> 
> - **Upload and download**
> - **SharePoint**
> - **Azure Blob Storage**
> - **Service Bus queue**
> - **Web service**
6. On a message with an internal document as source document, you can set up the data synchronization type.

When you run the message, you can indicate if the set up data synchronization must be used:

In the **Synchronization type** field, select an option.

> [!NOTE]
> **Note**
> 
> This field is only available if:
> 
> - The source document of the message is of one of these types:
>   - Internal document
>   - **ODBC** (or **ODBC Dynamics**)
> - The **Synchronization type** of the message is set to '**Table events**' or '**Date range**'.
  - **None**: The data synchronization setup of the message is not considered.
  - **All**: If the data synchronization type of the message is '**Table events**' or '**Date range**', these are not considered. The message is run as if the data synchronization type is '**All**'.
  - **Table events**: The data synchronization of type '**Table events**' is applied. Only select this option if the data synchronization type of the message also is '**Table events**'.
  - **Date range**: The data synchronization of type '**Date range**' is applied. Only select this option if the data synchronization type of the message also is '**Date range**'.
7. Sub-task: Set up batch processing.
  1. Expand the **Run in the background** section.
  2. In the **Batch processing** field, select an option. If **Yes**, also fill in the other fields.
  3. If desired, you can set up the recurrence for the project.

Click **Recurrence** and fill in the fields as desired.
  4. Click **OK**.
8. Click **OK**.

## Related

- [Set up data synchronization for message](/set-up-data-synchronization-for-message.md)
- [Run a message from custom code](/run-a-message-from-custom-code.md)
- [Run a message asynchronously](/run-a-message-asynchronously.md)
- [Custom services to run messages](/custom-services-to-run-messages.md)
- [Run message for testing purposes](/run-message-for-testing-purposes.md)
- [Run message test cases](/run-message-test-cases.md)
- [Field methods triggered during message run](/field-methods-triggered-during-message-run.md)