Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Azure Data Factory Activity Iterator Bug

Open
  • Is something wrong?
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, python
Domain
backend, testing-qa

Research direction

Start by placing pl_package_import.json in pipeline and test_package_import.py in tests, then run the supplied test to reproduce NoRemainingPipelineActivitiesMeetDependencyConditionsError. Inspect activity iteration and dependency evaluation around the Until loop, including the success and failure branches; done means the test completes and activities run in the expected order across iterations.

Written by the indexing model from the issue text.

Description

The activity iterator does not handle events in the same order that I would expect it to.

In the following scenario:

Image

With activities within the Until loop as below:

Image

The behaviour is not as would be expected. It appears that the addition of the failure condition to refresh the token causes the final activities (within the next If conditional) to not be evaluated. In addition, on the second iteration of the loop, the activities are evaluated out of sequence.

pl_package_import.json
test_package_import.py

Attached above are the files, to run successfully these would need to be added to a directory pipeline for pl_package_import.json and tests for test_package_import.py.

In this particular test, it is expected that it goes into the loop, then it processes the next activity in sequence. As it is incomplete, the condition should assess that it goes onto the next iteration of the Until loop. However, it raises exception NoRemainingPipelineActivitiesMeetDependencyConditionsError.

Removing lines 113 to 278 of the pipeline file fixes this, see the file below. This suggests that there is a bug where activities have a success and failure branch in terms of evaluating the next activities.
pl_package_import.json

I also note that the activities in the next iterations are evaluated out of order. For the second pl_package_import.json (i.e. the one that passes the test) where it compares if it goes into the if statement and runs a pipeline in the event of the conditional being false, the next activity should be a Wait activity, being the first one in the loop, but in reality it is the Web Activity, the second activity in the loop.

Dominant language
Python
Stars
135
Forks
43
Avg merge
1h 14m
Merged PRs (30d)
1

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/data-factory-testing-framework

All issues in microsoft/data-factory-testing-framework

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.