The Microsoft Dynamics 365 Asynchronous Processing Service (called the async service) executes long-running operations independent of the main Microsoft Dynamics 365 (online & on-premises) core operation. This results in improved overall system performance and improved scalability.
How does it work?
The
asynchronous service features a managed queue for the execution of asynchronous
plug-ins, workflows, and long-running operations such as bulk mail, bulk
import, and campaign activity propagation.
These operations are registered with the asynchronous service and are
executed periodically when the service processes its queue. Since these
operations are queued up and must be executed in time globally, there are some
well-defined resource quotas that enable resources to be distributed amongst
all online customers equally.
Where I can see these Jobs running?
A System Job also known as
an asynchronous operation, is used to define and track the execution of
asynchronous operations for example an asynchronous registered plug-in,
workflow, or other background system operation.
The following table lists the states, and the statuses for each state,
of an AsyncOperation.
An asynchronous operation can be made dependent on another
asynchronous operation. A dependent asynchronous operation does not execute
until the operation that it is dependent on has finished executing.
Refer here to know about - Dynamic CRM Sandbox Service
No comments:
Post a Comment