I have a Task in Task Scheduler with multiple triggers defined.
Trigger 1: Runs on the weekend every 4 hours during the day.
Trigger 2: Runs the task every 15 min every day; this one is for testing.
When I left last night, I disabled the test trigger but when I came in to work, the task had run multiple times despite the trigger being disabled and it not being a weekend (meaning the other trigger shouldn't have gone off). Any ideas what might cause this? My OS is Windows 10 Pro.
Related
How can I prevent future occurrences from running on a Task where I set the Repeat option when triggering the task. Let's say I started a task at 1:00 PM and told it to repeat every 5 minutes for 1 hour. Is there a way to prevent or cancel remaining events from firing prior to the task ending (e.g. after 7 of the 12 have run)?
I have some scheduled daily running pipelines.
Sometimes the scheduled trigger start time [Run start time] gets offset by few seconds [1s to 5s].
This is happening to all the pipelines having the same trigger.
Some of pipes use IR and some of them don't.
Trying to understand why it's happening.
Ex. Pipeline trigger offset by 1 second
Ashwin, yes this happens sometimes maybe due to a lag / latency between a trigger to start and actual start of a pipeline just like you clicking a button and time taken by the event behind that button to occur
But this does not hamper the execution of your pipeline
I have pipelines that I need to run in sequence. The first is a "raw to bronze," which runs daily at 4am. Once that completes, I want my "bronze to silver" to kick off. Raw to bronze is running just as expected (tumbling window every 24 hours), and it successfully completes. Bronze to silver is configured as a tumbling window trigger with dependency on raw to bronze, but its window is stuck in November 2021. I have tried combinations of offset and window size (0 offset to fire immediately, and a +4 hour window size to run in the next 4 hours), but the problem remains. I have also deleted and re-created the trigger. Still the dependency window is November 2021.
raw to bronze configuration:
bronze to silver configuration:
And when I look at trigger runs, I see the window is stuck in the past:
Any ideas what I might be missing? All I am wanting is for the bronze to silver to kick off immediately after raw to bronze completes. Raw to bronze takes about an hour to run.
Thanks in advance for any help!
I repro’d in my lab, and it worked when I started the 2nd tumbling trigger (which is dependent on trigger 1) a minute before the dependency trigger (A_to_B).
Tumbling trigger A_to_B:
Tumbling trigger B_to_C:
Created this trigger to start 1 min earlier than the dependency trigger (A_to_B).
While creating it, it asks to re-align offset for dependency by the difference time as shown in the below snip.
Trigger runs:
First B_to_C trigger starts with status as waiting on dependency. A minute later A_to_B trigger starts running and when completes it changes the status to succeed. Now B_to_C trigger starts running and completes successfully.
I have a ADFV2 trigger that runs every 2 minutes. The pipeline that is called usually takes just over a minute to run but sometimes it takes over 2 minutes but if that happens the trigger kicks in again and runs regardless of the previous trigger still running or not. Is there any way to stop this overlap?
The trigger needs to run every 2 minutes.
Thanks.
There is a concurrency setting in the pipeline definition. Set it to 1. The trigger will create an event, but it will be set to Queued state until previous job completes
I need to create schedulers to execute jobs(class files) at specified intervals..For Now, I'm using Quartz Scheduler which triggers the jobs at defined intervals from the time of triggering of it.
For Eg: Consider I'm giving a cron expression to run for every one hour starting at morning 9.My first run will be at 9 and my second run will be at 10 and so on.
If my job is taking 20 minutes to execute then in that case this method is not that much efficient.
What I need to do is to schedule a job for every one hour from the completion time of the previously ran job
For Eg: Consider my job to run every one hour is triggered at 9 and for the first run it took 20 minutes to run, so for the next time the job should trigger only at 10:20 instead of 10 (ie., one hour from the completion of previous ran job)
I need to know whether there are any methods in Quartz Scheduling to achieve this or any other logic I need to do.
If anyone could help me out on this,it would be very helpful for me.
You can easily achieve this by job-chaining your job executions. There are various approaches you can choose from:
(1) Implement a Quartz JobListener and in its jobWasExecuted method, that is invoked by Quartz whenever a job finishes executing, re-fire your job.
(2) Look at the Quartz JobChainingJobListener that you can use to implement simple job chaining scenarios. Please note that the functionality of this listener is very limited as it does not allow you to insert delays between job executions, there is no support for conditions that must be met before target jobs are executed etc. But you can use it as a good starting point to implement (1).
(3) Use QuartzDesk (our commercial product) or any other product that allows you to create job chains while externalizing and managing all job dependencies outside of your application. A job chain can have multiple target jobs that can be executed immediately, with a fixed delay or at arbitrary time in the future produced by a JavaScript expression. It also allows you to implement somewhat more sophisticated works flows, such as firing a target job when multiple source jobs complete their execution etc. I am attaching screenshots showing you what a simple job chain that re-executes Job1 with a 1 minute delay upon Job1's completion (with any job execution status) looks like: