Asynchronous service in Dynamics 365 Customer Engagement
The asynchronous service executes long-running operations independent of the main Dynamics 365 for Customer Engagement core operation. This results in improved overall system performance and improved scalability. The asynchronous service features a managed queue for the execution of asynchronous registered plug-ins, workflows, and operations such as bulk mail, bulk import, and campaign activity propagation. These operations are registered with the asynchronous service and executed periodically when the service processes its queue. The asynchronous service can be hosted on a server other that the server running Dynamics 365 Customer Engagement (on-premises).
In This Section
Asynchronous Service Architecture
Asynchronous Operation (system job) Entity
Dependency and Execution Order in Asynchronous Operations
Recurrence Pattern in Asynchronous Job Execution
Supported Entities for Asynchronous Operations
Walkthrough: Stop and Start the Asynchronous Service
Related Sections
Processes in Dynamics 365 Customer Engagement (on-premises) (formerly Workflows)
Data Management in Dynamics 365 Customer Engagement (on-premises)
Note
Can you tell us about your documentation language preferences? Take a short survey.
The survey will take about seven minutes. No personal data is collected (privacy statement).