Scheduler

Azure Scheduler allows you to invoke actions that call HTTP/S endpoints or post messages to a storage queue on any schedule. In Scheduler, you can create jobs that reliably call services either inside or outside of Windows Azure and run those jobs right away, on a regular or irregular schedule, or set them to run at a future date.

If you have any feedback on Azure Scheduler, we’d love to hear it.

  1. Allow scheduling jobs based on timezone

    Currently, you can only schedule jobs based on a fixed time offset from GMT. This means the actual local time when the job runs will change one hour forward or backward, in spring and fall when daylight savings change.

    236 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  10 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Scheduler support for TLS 1.2

    Hi,

    Our technical team has raised an issue and confirmed with MS that Scheduler currently only supports TLS 1.0.

    Please add support for TLS 1.2. We are trying to use scheduler to initiate Azure Functions running in an ASE in a private VNET. We had planned to have an API receive these triggers from scheduler. We are unwilling to enable TLS 1.0 support on our Azure Application Gateway (AAG) so Scheduler is unable to communicate with the API we planned to create.

    Thanks, Matt

    235 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Customizable timeout to a scheduled job through Azure Portal

    Add the ability to customize the timeout interval through the Azure portal.
    This feature is right now only available through API.

    121 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Mr. Andersson,
    To be clear, do you mean the retry policy for an HTTP request (which includes the timespan between retries and the number of retry attempts to make)?

    Thanks,
    Kevin

  4. Email alert if HTTP/S response status is 4xx or 5xx

    Maybe this feature exists already, but I can't see it...

    It would be great to be alerted via email if any of my HTTP/S jobs fail.

    This could be DNS resolution failure, or a response with a code of 4xx or 5xx.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Mr. Boot,
    Thank you for your feedback. In the meantime you can create an error action on the job that is configured to send an email via a service like SendGrid or a text message via a service like Twilio.

    -Kevin Lam

  5. Azure Scheduler support for variables

    Having the possibility to use date variables in azure scheduler POST requests would allow us for example to make a REST call to azure table storage like 'delete all records before {DateTime.UtcNow.AddMonths(-1)}'.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  API & SDK  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    It would be helpful to hear which variables would be most useful to everyone by adding them to the comments of this suggestion.

    Thanks,
    Kevin

  6. Disable wrapping message with StorageQueueMessage XML

    We would like an option to prevent the scheduler from wrapping the message with StorageQueueMessage XML. There is no indication in the portal that Azure will alter our message text.

    We insert into our queues from the scheduler and our own code. Our messages are JSON strings. It's very inconvenient and inefficient to have to serialize and deserialize multiple times to get/put our message.

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API & SDK  ·  Flag idea as inappropriate…  ·  Admin →
  7. Information about scheduler task and way to terminate it

    For example when you have created your scheduler job and you click run once. You have no idea after that what's going on with the job and if for example you have made a error in your code and it's just looping endlessly you can't terminate and you are required to wait until the timeout.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow call internal endpoint or virtual network address

    I think that it could be useful to make http call to internal endpoind of "private" cloud services or vm inside a private azure vnet (not externally visible)

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Thanks for making the suggestion.
    This can be done by either opening a port on your VNET, using a Service Bus Relay endpoint, or installing Hybrid Connector.

    -Kevin

  9. Save UTC offset settings

    When we create a job, we can enter a UTC offset field.
    However, when we edit the job, the UTC setting is never saved and start-time and end-time fields are changed as UTC time, as if UTC settings were ignored.

    From the perspective of UX, UTC settings should be saved just as we enter the data. This specification may confuse Azure Scheduler users.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  10. Time fields should show 24-hour time

    Start-time field and End-time field now show 12-hour time; For example, '12:00:00 AM' or in Japanese locale, '12:00:00 午前'. However, we must type Chinese characters '午前' to input a date.
    In order to save trouble, it will be useful to show 24-hour time in those fields.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow me to create a schedule by specifying a schedule in a crontab format

    Crontab is a widely used anc concise scheduling format. There are numerous open source libraries for a variety of languages available for parsing the format already written.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API & SDK  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow scheduler to be "connected" to vnet, to allow access to hybrid services, running on premises

    To use Scheduler as centralized place to schedule our jobs on both Azure and on-premises Backend Services, we need the scheduler to be access them over Express Route and / or VPN.

    This can be achieved, if Scheduler can be assosiated with VNET.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add option to auto-delete completed one-time jobs

    This is more relevant for jobs that post messages to a queue.
    If you think about this scenario, this job is not the "real" job. It only sends a signal to the queue which then has to be processed somewhere else.

    In this case, I don't want this single one-time completed job to stay in the collection and account towards my quota. I would like it to be automatically deleted if everything was ok.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Mr. Frostlander,
    Thank you for your feedback, We can look at possibly adding a flag to a job that will automatically delete a successfully completed job.

    Regards,
    Kevin

  14. Insert a queue message into ARM Storage

    Storage queue action supports only Classic Storage.
    Today, customers tend to use a new deployment model: ARM. So it would be much better to start support for ARM Storage.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Access Job Status Information

    Scheduled jobs should expose an object that allows you to query the last run, next run, and schedule for the currently running job. There should also be some indication of whether the job succeeded for failed to allow for error handling logic to be incorporated into the job.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add more configurations for Storage Queue Action Type

    We use the scheduler service to start a long running job once a day. We want to set the expiration time to one day so that the service is not running in parallel or twice.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    I’m not exactly clear what you are looking for. Do you mean that you would like the message in the queue to expire (be deleted) if it has not been processed (read) by a certain time?

    Thanks for your suggestion,
    Kevin

  17. Advanced Scheduler Job Dependencies

    For example; Job 2 is dependent on job 1 finishing successfully before it can start.

    A job should not start unless all conditions are met besides a scheduled start time. 3 conditions in particular that would be very useful for this; Queued/waiting, failed and successful. Even more useful if a job could be configured to run an action if it has been sitting in a waiting state for x amount of time...

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Scheduler Jobs Storage Queue works with Resource Manager

    It appears that the "storage queue" action only works with "classic" storage accounts, and not the new "Resource Manager" Storage Accounts. It would be nice if the Scheduler worked with the new Storage Account type.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →

    Scheduler does work with resource manager storage accounts today but the portal currently only lists the classic storage accounts. Until we enable the ability to pick a resource manager storage account in the portal you can do it through the REST API today.

  19. Do not hide an 'Advanced Schedule' on Schedule blade

    The idea to hide an 'Advanced Schedule' on Schedule blade when minute or hour recurrence is selected is definitely an extremely bad idea!
    I was looking for advances scheduling for 6 hours today and even wrote my own ARM template for this. I've discovered the schedule service REST API, ARM schema, all PowerShell cmdlets, etc. But accidentally I've discovered that it is simply hidden! :)))
    Please, do not hide such things in UI.
    Disable them!

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  20. create a dashboard with the ability to see upcoming schedules

    We would like to see a dashboard that includes a comprehensive view of what is scheduled for a 24h period. This would show schedules from 12:00am to 11:59pm. I can see that "Nextrun" is data that is already available from the cmdlet "Get-AzureRmSchedulerJobCollection".
    Fields we would like to see are: Job name, job collection, status, start time, end time, and elapsed time.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Scheduler

Categories

Feedback and Knowledge Base