Skip to content

Commit

Permalink
Merge pull request #41 from vasilev/feature_remove_delay_and_task_del…
Browse files Browse the repository at this point in the history
…ay_from_scheduling_parameters

Removed ambiguous 'delay' and 'task_delay' from task scheduling
  • Loading branch information
treeder committed Apr 7, 2015
2 parents 2495c45 + 051bf93 commit 3fe8e94
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,8 +221,6 @@ puts schedule.id
- **priority**: Setting the priority of your job. Valid values are 0, 1, and 2. The default is 0. Higher values means tasks spend less time in the queue once they come off the schedule.
- **start_at**: The time the scheduled task should first be run.
- **timeout**: The maximum runtime of your task in seconds. No task can exceed 3600 seconds (60 minutes). The default is 3600 but can be set to a shorter duration.
- **delay**: The number of seconds to delay before scheduling the tasks. Default is 0.
- **task_delay**: The number of seconds to delay before actually queuing the task. Default is 0.
- **label**: Optional label for adding custom labels to scheduled tasks.
- **cluster**: cluster name ex: "high-mem" or "dedicated". This is a premium feature for customers to have access to more powerful or custom built worker solutions. Dedicated worker clusters exist for users who want to reserve a set number of workers just for their queued tasks. If not set default is set to "default" which is the public IronWorker cluster.

Expand Down

0 comments on commit 3fe8e94

Please sign in to comment.