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)?
Related
I want to implement a delay task and found a cadence cron example, how to use cadence to implement a delay task?
Cron is for periodic execution of some functionality.
If you need to delay a task you can call sleep and the beginning of the workflow and then call an activity that executes the task.
Cadence supports both activity and workflow delaying.
Activity delay can be achieved with Workflow.Sleep API
Workflow delay can be achieved with DelayStart option. See https://github.com/uber-go/cadence-client/blob/e66e2d4da8def80e7a5730b824a2de7a28f5c050/internal/client.go#L415
For regular workflows, this will delay execution that many seconds, then start.
For cron workflows, this will delay ONLY the FIRST execution. For example you want to set up an hourly cron workflow but you want it to start running from next week on Monday at 9AM. You can pass delayStart seconds option to delay till that Monday between 8AM and 9AM so it will start at 9AM since it's the next schedule.
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 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.
I know orchard has its default scheduler running in every minutes. Does it mean that the minimal interval is 1 minutes?
If I want a task to run in every 20 seconds, how can I make it.
Thanks
You can open the file src\Orchard.Web\Config\Sites.config to uncomment the Delay between background services executions paragraph. Here you can set the interval.
I have a Quartz Job that I want to fire every minute. The job itself contains logic to check to see if there is a process to run and if there is, this job could take 45 minutes to complete.
Using a Simple Trigger, will Quartz fire this job off every minute even if there is one already running? Or if the interval is set to 1 minute, does that mean that Quartz will wait 1 minute after the job is done before it fires the next job?
If the trigger is set to fire every minute, it will fire every minute (and a new job instance will be created and invoked).
Unless the related job is marked #DisallowConcurrentExecution.