In Salesforce, Tasks are tied to their related EmailMessage records. Salesforce can regenerate a Task whenever the EmailMessage is edited, resaved, or re-ingested after the ActivityId or related Task was deleted. The newly created Task is owned by EmailMessage.CreatedById. This is intended behavior.
This article answers why a Task associated with an EmailMessage reappears after you delete it, and what to do instead of deleting it.
Observe that Salesforce generates a new Task and repopulates EmailMessage.ActivityId with the Id of the new Task.
Deleting the Task that the ActivityId on the EmailMessage points to is not a sustainable approach. Any EmailMessage resave can trigger Task re-creation with the OwnerId inherited from EmailMessage.CreatedById.
Instead of deleting proxy Tasks, use Task Restriction Rules to isolate proxy Tasks from visibility to all users. This avoids the deletion and re-creation cycle entirely, while still preventing users from seeing these system-generated proxy Tasks.
005460239

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.