Can you please provide a snippet of your implementation?

trigger_scheduler.add_dataset_trigger(schedule_task_id=TASK_ID, schedule_queue='default',
trigger_project='Cassava Leaf Disease Classification', name='start task on data - End Game')

then I use trigger_scheduler.start()

In this case, it would wait until any change occurred in the project mentioned here. Even if a task started, and not a dataset change or publish or anything, it would trigger.

So in my case where I schedule a task every time I publish a data, when I publish my dataset once, it triggers and starts a new task.

However, since a new task started in the project, it would again start a new task.

recursively.

I'm curious as to if this is buggy behavior or if it is expected?

Let me play with it a bit and see if I can find more 🙂

I just assumed it should only be triggered by dataset related things but after a lot of experimenting i realized its also triggered by tasks, if the only condition passed is dataset_project and no other specific trigger condition like on publish or on tags are added.

I just assumed it should only be triggered by dataset related things but after a lot of experimenting i realized its also triggered by tasks...

VexedCat68 I think you are correct, and it should only be triggered by "Dataset" Tasks, that said maybe there is a bug , in which case if there are no additional filters it will get triggered on Any change in the project. This will explain how adding the tags filter solved the issue.
wdyt?

Agreed. The issue does not occur when I set the trigger_on_publish to True, or when I use tag matching.

Nice, that seems to be the issue. Any chance you can open a GitHub issue, so we do not loose track of it ?

I'll do that.

do I just post the issue on the main clearml repo?

main clearml repo?

Yep that sounds right 🙂 thank you!

Done