question

Sudarsan-6786 avatar image
0 Votes"
Sudarsan-6786 asked MartinJaffer-MSFT answered

Pipeline manual trigger takes 3 hours for run to complete

Pipeline run id:5f8c06bd-9f6e-4f07-a2f6-790286f47a26
This pipeline finishes usually in 1 hour.**Would like to know why it took 2 hours 42 minutes to complete in final task alone of 2 hours 5 minutes.**Have to explain .

Finalize Staging Data
Copy data
9/23/21, 1:38:09 PM
02:05:48
Succeeded
sqlserverintegrationRuntime (North Europe)
134625-image.png

The same pipeline when run in the scheduler takes more time to execute task and hence session id get failed.**Why is there a difference of time when running in scheduler and doing a adhoc run*.*Below is scheduler run id
Pipeline run id:607b282d-4595-4698-9fec-b9b1993683a7
Error in task:








azure-data-factory
image.png (14.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

MartinJaffer-MSFT avatar image
0 Votes"
MartinJaffer-MSFT answered

Hello anonymous user-6786 and welcome to Microsoft Q&A.

Ideally there should not be a difference between a "Trigger now" and "scheduled" run. There will be a difference between that and a "debug run", as debug run uses a different compute.

Investigation of performance issues are usually better handled by a support ticket. Once a support ticket has been opened and permission given, more personalized tools can be brought to bear on the issue.

Would you like to open a support case? If you do not have a support plan, I can give you a 1-time free support ticket.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.