Forum Discussion
del
5 years agoContributor III
The combination of your posts:
and
indicates to me that the error is within your SQL Server and has nothing to do with the Task Execute being deprecated. I think the “deadlock victim” error needs to be evaluated first with your DBA or DBD before trying to fix the issue by pipeline modifications. Then move on to the Pipeline Execute after the DB error is fixed.
(note: I typed this up before I fully read Kory’s post, so it may be redundant; but I submitted anyway in case it helps)