When and Why Do You Use the "Deactivated" State in Activity Settings?

[HamidBee]

Hi everyone,

I’m working on building data pipelines in Microsoft Fabric and noticed the option to set an activity’s state to "Deactivated" in the settings. I understand that this prevents the activity from executing within the pipeline, but I’m curious to know more about the practical applications of this feature.

For those with experience, when do you typically use the "Deactivated" state? Are there specific scenarios where it’s particularly useful? I’d love to hear your insights on why and how you use this functionality in your workflows.

Thanks in advance!

[Srisakthi · Accepted solution]

Hi @HamidBee ,

I would prefer "Deactivate" in these cases

1. After certain period of development I may not require certain activity due to requirement changes , in that case I do want to keep my activity in deactivated state so that if required i can enable it again. 

2. To know what happened earlier in my pipeline runs with those activities. I can revisit it anytime by keeping it in "deactivated state".

Regards,

Srisakthi