question

50697303 avatar image
0 Votes"
50697303 asked PRADEEPCHEEKATLA-MSFT edited

Are these time trigger reliable way to run prod pipelines? Our time triggerred job didn't run, no errors, no way to debug that I know.

Our time schedule job didn't run, delaying the production data. The workflow iteration is just missing from the report, there are no errors shown. This has happened multiple times for us, creating live sites. Is ADF time schedule known to be buggy like this? Any better way of scheduling/monitoring such regularly scheduled jobs?

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.

1 Answer

SandervandeVelde42 avatar image
0 Votes"
SandervandeVelde42 answered 50697303 commented

Hello @KshitizKSharma-5362 ,

are you referring to the Azure Function Timer trigger?

These timer triggers can act a bit counter intuitive.

I also encountered issues in the past when I ran multiple triggers on the same server.

Please check this blog post for background information and pointers.


· 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.

I meant 'Scheduletrigger' for ADF pipelines. We did more investigation and found that particular trigger isn't reliable at all - any deployment around the trigger time can disable it and pipeline just skips the slot. Multiple deployments mean multiple misses. There should be a warning on jobs using this or just give it more appropriate name like 'UnreliableScheduleTrigger' so users are aware of problems when creating jobs on it.
We're going to switch to tumbling window trigger to avoid this problem in future.

0 Votes 0 ·