ADF issue in running Scope activity

Question

ADF issue in running Scope activity

Balaji Krish 0 Microsoft Employee

n Azure Data Factory, I have setup a Pipeline that runs a Scope script activity against Asimov VC to aggregate data. I am finding that the activity is failing whenever it runs for more than 3 hours+. The activity error I see is

Error code

BadRequest

Failure typeUser configuration issue

Details

Operation on target TBP failed:

Activity ID

c031b11a-f69d-491e-9e55-639517a7b0e3

In ADF I have the activity timeout configured for 12 hours. So looks like some cosmos related timeout is happening in when running the scope activity. I couldn't find any meaningful way to troubleshoot.

Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-08T22:00:51.1666667+00:00
Hi @Balaji Krish
Thank you for reaching out regarding the issue.

Based on the information provided, we understand that your Azure Data Factory Scope Script activity fails when the execution runs for more than approximately 3 hours, even though the activity timeout in ADF is configured for 12 hours.

To help us investigate this further, could you please provide the following information in private message.

Azure Data Factory (ADF) name

Subscription ID

Region

Pipeline name

Pipeline Run ID of a failed execution

Activity name

Approximate failure time (UTC)

The complete activity output/error JSON from the failed activity

The Scope script (or a sanitized version, if it contains sensitive information)

Has this pipeline ever completed successfully for similar data volumes?

Does the failure consistently occur after around 3 hours, or does the duration vary?

Have there been any recent changes to the pipeline, Scope script, data volume, or environment?

Additionally, if possible, please let us know whether the Scope script completes successfully when executed outside of Azure Data Factory (if applicable).

Once we receive the above information, we will analyze the logs to determine whether the failure is occurring within Azure Data Factory or the underlying Scope execution service and proceed with the appropriate next steps.

We appreciate your cooperation and look forward to your response.
Balaji Krish 0 Reputation points Microsoft Employee

2026-07-08T22:34:02.7166667+00:00
Thank you for getting back to me. Answers below:

Azure Data Factory (ADF) name :

Subscription ID :

Region:

Pipeline name:

Pipeline Run ID of a failed execution: 89585f73-ccf6-4ee5-947f-604975aa87d6

Activity name: TBP

Approximate failure time (UTC): 7/8/2026, 3:11:33 AM

The complete activity output/error JSON from the failed activity Error code BadRequest Failure typeUser configuration issue Details Operation on target TBP failed: Activity ID Error source Pipeline

The Scope script (or a sanitized version, if it contains sensitive information) The scope script definition is part of the TBP activity

Has this pipeline ever completed successfully for similar data volumes? yes

Does the failure consistently occur after around 3 hours, or does the duration vary? yes around 3 hours 9 minutes of TBP activity run always fails

Have there been any recent changes to the pipeline, Scope script, data volume, or environment? No
Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-12T00:11:56.2333333+00:00
Thank you for providing the requested information.

Based on the details you've shared, we observe that:

The pipeline has completed successfully for similar workloads in the past.

No recent changes have been made to the pipeline, Scope script, data volume, or environment.

The failure consistently occurs after approximately 3 hours and 9 minutes, despite the Azure Data Factory activity timeout being configured for 12 hours.

The activity returns only a generic BadRequest error without additional diagnostic details.

Since the issue is consistently reproducible and the available activity output does not provide sufficient information to determine the root cause, we will proceed with a deeper investigation using the Pipeline Run ID, Activity ID, and failure timestamp you've provided.

We'll review the backend execution logs to determine whether the failure originates from Azure Data Factory orchestration or the underlying Scope execution service.

We'll keep you updated as soon as we have more information. Thank you for your patience.
Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-14T19:05:13.6733333+00:00

Hi @Balaji Krish
Did you get any chance to review the above response. Thank you!

1 answer

Your answer

Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-08T22:00:51.1666667+00:00

Hi @Balaji Krish
Thank you for reaching out regarding the issue.

Based on the information provided, we understand that your Azure Data Factory Scope Script activity fails when the execution runs for more than approximately 3 hours, even though the activity timeout in ADF is configured for 12 hours.

To help us investigate this further, could you please provide the following information in private message.

Azure Data Factory (ADF) name

Subscription ID

Region

Pipeline name

Pipeline Run ID of a failed execution

Activity name

Approximate failure time (UTC)

The complete activity output/error JSON from the failed activity

The Scope script (or a sanitized version, if it contains sensitive information)

Has this pipeline ever completed successfully for similar data volumes?

Does the failure consistently occur after around 3 hours, or does the duration vary?

Have there been any recent changes to the pipeline, Scope script, data volume, or environment?

Additionally, if possible, please let us know whether the Scope script completes successfully when executed outside of Azure Data Factory (if applicable).

Once we receive the above information, we will analyze the logs to determine whether the failure is occurring within Azure Data Factory or the underlying Scope execution service and proceed with the appropriate next steps.

We appreciate your cooperation and look forward to your response.
Balaji Krish 0 Reputation points Microsoft Employee

2026-07-08T22:34:02.7166667+00:00

Thank you for getting back to me. Answers below:

Azure Data Factory (ADF) name :

Subscription ID :

Region:

Pipeline name:

Pipeline Run ID of a failed execution: 89585f73-ccf6-4ee5-947f-604975aa87d6

Activity name: TBP

Approximate failure time (UTC): 7/8/2026, 3:11:33 AM

The complete activity output/error JSON from the failed activity Error code BadRequest Failure typeUser configuration issue Details Operation on target TBP failed: Activity ID Error source Pipeline

The Scope script (or a sanitized version, if it contains sensitive information) The scope script definition is part of the TBP activity

Has this pipeline ever completed successfully for similar data volumes? yes

Does the failure consistently occur after around 3 hours, or does the duration vary? yes around 3 hours 9 minutes of TBP activity run always fails

Have there been any recent changes to the pipeline, Scope script, data volume, or environment? No
Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-12T00:11:56.2333333+00:00

Thank you for providing the requested information.

Based on the details you've shared, we observe that:

The pipeline has completed successfully for similar workloads in the past.

No recent changes have been made to the pipeline, Scope script, data volume, or environment.

The failure consistently occurs after approximately 3 hours and 9 minutes, despite the Azure Data Factory activity timeout being configured for 12 hours.

The activity returns only a generic BadRequest error without additional diagnostic details.

Since the issue is consistently reproducible and the available activity output does not provide sufficient information to determine the root cause, we will proceed with a deeper investigation using the Pipeline Run ID, Activity ID, and failure timestamp you've provided.

We'll review the backend execution logs to determine whether the failure originates from Azure Data Factory orchestration or the underlying Scope execution service.

We'll keep you updated as soon as we have more information. Thank you for your patience.
Pilladi Padma Sai Manisha 11,350 Reputation points Microsoft External Staff Moderator

2026-07-14T19:05:13.6733333+00:00

Hi @Balaji Krish
Did you get any chance to review the above response. Thank you!

Answer 1

Hi Balaji,

The 12-hour timeout in ADF only controls the ADF activity policy. It does not always override timeout limits in the downstream service that the activity is calling.

Since the failure happens only when the Scope job runs for more than 3 hours, I would first treat this as a downstream Scope/Asimov VC execution timeout or service-side limit, not a normal ADF pipeline timeout.

Please check the following:

Open the failed activity in ADF Monitor and expand the full input/output JSON. Sometimes the inner error is available there even when the UI only shows BadRequest.

Check the Scope/Asimov job execution logs using the Activity ID and UTC timestamp:

c031b11a-f69d-491e-9e55-639517a7b0e3

If the same script consistently crosses 3 hours, try splitting it by smaller time windows/partitions, for example hourly or daily slices, and run them through a ForEach pattern.
If this is calling an internal VC/service through ADF, confirm whether that service has its own max execution/session timeout around 3 hours.
Add ADF retry only if the operation is idempotent. Otherwise retries may duplicate output.
If possible, change the pattern to submit the Scope job asynchronously, then poll the job status from ADF instead of keeping one long-running synchronous activity open.
In short, the ADF timeout setting looks fine, but the failing component is probably the Scope/Asimov execution path. I would collect the full activity output and backend job logs, then either split the workload or move to an async submit-and-poll pattern.