Campaign - Microsoft Dynamics 365 integration workflows
The Workflows page lists the technical workflows and their status.
The integration application comes with three workflows:
Microsoft Dynamics 365 to Campaign
- Send contacts from Microsoft Dynamics 365 into Adobe Campaign
- Custom entities: Bring in custom tables from Microsoft Dynamics 365 to Adobe Campaign. Learn more
- This is also known as Ingress (referring to the ingress of data from Microsoft Dynamics 365 to Adobe Campaign)
Campaign to Microsoft Dynamics 365
- Email marketing events from Adobe Campaign Standard are sent to Dynamics 365 (email send, open, click, bounce). Learn more
- This is also known as Egress (referring to the egress of data from Adobe Campaign to Microsoft Dynamics 365)
Opt-In/Out
Opt-out statuses (e.g., denyList) can be synchronized from Microsoft Dynamics 365 to Adobe Campaign or from Adobe Campaign to Microsoft Dynamics 365. The data can also by synchronized bidirectionally (i.e. data flows in both directions). Learn more.
Workflow backlog
This integration application first reads in data and then writes data to the destination. The Backlog column indicates the number of records that have been queued and are waiting to be written. This value is expected to grow when you have a large amount of data to process (e.g., you are running the integration for the first time, you are replaying the data, etc.).
Workflow status workflow-status
The Status column indicates the state of the background processes associated with the workflow. Possible values are:
- RUNNING: The process is currently running and your data should be synchronized.
- STOPPED: The process is not currently running, so you should not expect your data should be synchronized.
- STARTING: You have requested that the workflow processes to start. The application has not yet started to synchronize the data associated with this workflow, but you can expect it will after a few minutes (when it will then show the status of RUNNING)
- FAILED: The workflow processes were running but they encountered error(s) and they could not recover from these.
Available actions
Possible actions are listed below.
-
Edit: Clicking the pencil icon will send you to another page that will allow you to make updates to the workflow. Keep in mind that any changes you make will NOT take effect until you stop the workflow and then restart it.
-
Start: A Start button requests that a stopped workflow be started. This button will only appear when the processes associated with the workflow are currently stopped. The processes will first change to “STARTING” and then to “RUNNING”. The data associated with the workflow will not start synching until the workflow is in a “RUNNING” state.
The start button is a toggle. If the workflow processes have been started already, the button will change to a Stop button.
-
Stop: A Stop button requests that a running workflow be stopped. This button will only appear when the processes associated with the workflow are currently running.
When you edit a workflow, your updates are NOT immediately incorporated into the running processes’ rules, until you stop the workflow and then click the Start button. Then your updates are incorporated into the running processes (once the process returns to a RUNNING state).
A warning indication is added to the Stop button to let you know when you have (a) made updates to workflow, but (b) have not done a Stop/Start of this workflow.
