[BUG] ADF Activity Runs query can't do pagination

[rnicholson14]

Library name and version

Azure.ResourceManager.DataFactory 1.11.0

Describe the bug

Can't query more than 100 ActivityRuns via API because ContinuationToken is not exposed.
Only way to call Activity Runs -Query By Pipeline Run is by calling DataFactoryResource.GetActivityRunAsync.
Problem is that all you get from this call is AsyncPageable<PipelineActivityRunInformation> which means ContinuationToken value is lost...
Since pagination is implemented via RunFilterContent property it means "default" nextLink logic for pages can't work.

This same issue existed for DataFactoryResource.GetPipelineRunsAsync and #39438 was created and resolved in #42247

Expected behavior

All activities from the pipeline run id meeting the RunFilterContent are returned.

Actual behavior

Only returns first page (100 rows) and no way to do pagination

Reproduction Steps

Execute dataFactoryResource.GetActivityRunAsync(pipelineRunId, runFilterContent) for a pipeline run with over 100 activities, and only the first page (100 activities) will be returned.

Environment

Visual Studio 2026 18.4.2

[github-actions]

//cc: @ArthurMa1978

[github-actions]

🎯 Agentic Issue Triage

Thank you for your feedback. Tagging and routing to the team member best able to assist.

Summary: This bug reports that DataFactoryResource.GetActivityRunAsync returns only the first page (100 rows) of activity runs with no mechanism to retrieve subsequent pages, because the ContinuationToken used for pagination in the underlying API (Activity Runs - Query By Pipeline Run) is not exposed through the SDK's AsyncPageable abstraction.

📋 Issue Analysis

Package: Azure.ResourceManager.DataFactory 1.11.0
Category: Mgmt (Azure.ResourceManager.* SDK)
Service: Data Factory

Root Cause: The Data Factory pagination model for Activity Runs uses a ContinuationToken within RunFilterContent (request body) rather than a standard nextLink URL in the response. The SDK wraps the result in AsyncPageable<T>, but without threading the continuation token through successive page requests, only the first 100 results are returned.

Precedent: This is a known pattern — the same issue previously occurred with DataFactoryResource.GetPipelineRunsAsync, which was reported in #39438 and resolved in #42247. The fix there exposed continuation token handling properly; the same approach should be applicable here.

🔍 Reproduction

Call dataFactoryResource.GetActivityRunAsync(pipelineRunId, runFilterContent) against a pipeline run with more than 100 activities. Only the first 100 are returned with no way to retrieve the rest.

🔧 Suggested Fix Direction

• Review how fix(adf): DataFactoryResource.GetPipelineRuns cannot do pagination #42247 resolved the same issue for GetPipelineRunsAsync and apply the same pattern to GetActivityRunAsync
• Expose a pageable mechanism that properly threads the ContinuationToken from each response page back into the next request's RunFilterContent
• Relevant REST API: [Activity Runs - Query By Pipeline Run]((learn.microsoft.com/redacted)

🏷️ Label Confidence

Confidence: High

• The issue explicitly names Azure.ResourceManager.DataFactory, which clearly maps to service label Data Factory and category label Mgmt
• Validated against quality reference issues: [FEATURE REQ] Dataverse linked service SDK #51254, Is .Net6 not supported by Azure.ResourceMabager.DataFactory ? #41492, Unable to create ADF Azure Storage Linked Services #36099 — all use the same Data Factory + Mgmt label combination
• No label ambiguity; no similar open duplicate issues found

Generated by Agentic Triage for issue #57588 · ◷

[rnicholson14]

Created pull request #57603 to address this issue