question

BrentLeslie-2638 avatar image
0 Votes"
BrentLeslie-2638 asked BrentLeslie-2638 edited

Data Factory Weekly Triggers not working in Australia?

I set up a trigger to run once per week, at a particular UTC time, published the trigger then waited for it to run. It didn't run, nor did it log any results. So I switched the trigger to be daily, running it a few minutes later. The trigger ran fine. I tried setting it back to run weekly, with every day selected. It still didn't run.

It seems the weekly trigger is broken? Our ADF is in Australia East, so not sure if it is related to just that data centre or region.

36181-adftriggerproblem.png


azure-data-factory
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PRADEEPCHEEKATLA-MSFT avatar image
0 Votes"
PRADEEPCHEEKATLA-MSFT answered BrentLeslie-2638 commented

Hello @BrentLeslie-2638,

Welcome to the Microsoft Q&A platform.

As per repro from my end, the Azure Data Factory weekly trigger works as expected without any issue.

Note: I have tested in Azure Data Factory located in Australia East.

36296-adf-trigger.gif

When creating a schedule trigger, you specify a schedule (start date, recurrence, end date etc.) for the trigger, and associate with a pipeline. Pipelines and triggers have a many-to-many relationship. Multiple triggers can kick off a single pipeline. A single trigger can kick off multiple pipelines.

Couple of things to note while using the schedule triggers.

  • While creating a new trigger, make sure to select the Activated option set to Yes.

36306-image.png

  • Make sure the created trigger should be associated with the pipeline.

36307-image.png

  • Make sure to Publish all to publish the changes to Data Factory. Until you publish the changes to Data Factory, the trigger doesn't start triggering the pipeline runs.

36250-image.png

Reference: Azure Data Factory - Create a trigger that runs a pipeline on a schedule

Hope this helps. Do let us know if you any further queries.


  • Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

  • Want a reminder to come back and check responses? Here is how to subscribe to a notification.



adf-trigger.gif (526.0 KiB)
image.png (47.2 KiB)
image.png (119.6 KiB)
image.png (25.8 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hmmm, this has worked on day 2 and on day 3 (see my note below for me testing it - that was on Monday, day 1). I suspect the rollout wasn't complete on the first day, but it appears to be functioning correctly now. Thanks!

0 Votes 0 ·
BrentLeslie-2638 avatar image
0 Votes"
BrentLeslie-2638 answered

@PRADEEPCHEEKATLA-MSFT

Yes, I ensured it was Activated, UTC time was right and it was published, still didn't work.

Are you using a different interface? Note that I don't have an option for a Time Zone in my original picture, only UTC...

Hang on, it looks like you may have been mid-release of the Time Zone feature listed here: https://feedback.azure.com/forums/270578-data-factory/suggestions/35771716-support-for-daylight-savings-time-for-trigger-sche

I guess if I was using it while you were doing the release, it may have not worked. I hadn't reloaded the data factory interface for some time, so may have had the old interface trying to write with a new backend.

Trying again, I am setting up a new trigger named "TestTrigger2" with the new Time Zone option:


36605-adferror1.png


I then hit the Publish button, 3 minutes before the trigger should occur:

36606-adferror2.png

A few seconds later, the pipeline is published with the new trigger. This occurs with at least 2 minutes before the pipeline is due to be triggered.

I wait 5 minutes, then I check if the trigger has run:

36665-adferror3.png

TestTrigger2 has not run (the listed one is from a previous run, that is setup to run Daily, which appears to work).

Am I doing something wrong? PM me if you want to look at this particular data factory.


adferror1.png (91.4 KiB)
adferror2.png (122.0 KiB)
adferror3.png (81.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TangTao-7296 avatar image
0 Votes"
TangTao-7296 answered BrentLeslie-2638 edited

@BrentLeslie-2638 ,

Did you publish it to adf_publish branch after making changes on the original trigger?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, this was a bug in data factory that now appears fixed. You couldn't set a trigger to a time in the very near future as it took a while for the trigger to be active. It seems that this has been fixed somewhere along the way as the behaviour is now not the same as it previously was.

1 Vote 1 ·