Question

You register a synchronous plug-in on the Post-Operation stage of the Update message for the Account table. Inside the plug-in you use the IOrganizationService from the execution context to create a related Task record. During testing, an unrelated downstream synchronous plug-in throws an exception after your plug-in completes, and you observe that the Task record you created is NOT persisted in Dataverse. Why does the Task creation get rolled back?

Accepted Answer

Synchronous plug-ins registered in the Post-Operation stage execute within the same database transaction as the core operation, so any later exception rolls back all changes made in that transaction.

Answer

The Post-Operation stage always runs outside the transaction, so the rollback is caused by the Organization service caching the create until the pipeline ends.

Answer

Records created via IOrganizationService in a plug-in are only committed when you explicitly call a Save or Commit method, which the plug-in did not do.

Answer

Task records are always created asynchronously by the platform, so the system job was cancelled when the downstream plug-in failed.