topic Re: Duplicate Annotations Generated When Refreshing Triggers Page in Pipelines

Duplicate Annotations Generated When Refreshing Triggers Page

Anonymous — Mon, 05 Aug 2024 17:05:16 GMT

In both our development and higher environments, we are seeing annotations duplicate every time we click the Refresh icon on the Manage > Triggers page.

If you refresh the browser window, they go away. The duplicates do not save unless you click OK from the edit panel. Then they are saved in the trigger definition.

Before refresh:

After refresh:

Re: Duplicate Annotations Generated When Refreshing Triggers Page

Anonymous — Tue, 06 Aug 2024 02:10:05 GMT

Hi Anonymous ,

Duplicate annotations in Data Factory can occur for several reasons:

1. If annotations are manually added, there might be accidental duplication due to human error.

2. If you’re using scripts or automated processes to add annotations, there might be a bug or oversight causing the same annotation to be added multiple times.

3. When pipelines or datasets are cloned, the annotations might be duplicated if not properly managed.

4. Azure Data Factory does not inherently prevent duplicate annotations, so without custom validation, duplicates can easily occur.

To avoid this, you can implement checks in your automation scripts or manually review annotations to ensure they are unique. You can read this document: Monitor Azure Data Factory and Azure Synapse Analytics pipelines with annotations and user properties - Azure Data Factory | Microsoft Learn

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Duplicate Annotations Generated When Refreshing Triggers Page

Anonymous — Tue, 06 Aug 2024 13:44:24 GMT

Hi Yilong,

None of these are reasons for the duplicates. The duplicates are appearing when clicking the Refresh button within Azure Data Factory.

Re: Duplicate Annotations Generated When Refreshing Triggers Page

Anonymous — Wed, 16 Apr 2025 15:40:30 GMT

Can anyone from Microsoft chime in? Is this reproducable or a known issue? Still experiencing it with our instance of ADF.