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
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.
This would aid debugging services that pull jobs from the queue placed by the scheduler4 votes
We will look into including a sample preview of the message in the portal.
- Scheduler Job Collection blade > Add
- Add a job and click OK.
- Return to Scheduler Job Collection blade, but Monitoring section is not refreshed job list.
So, it would be good to add Refresh button on the Scheduler Job Collection blade.4 votes
The idea is to send with my Http Get request some dynamic parameters like the last time this particular job ran, so I could add to my Uri something like "http://myapi.domain/CallFromScheduler?lasttime=@JobLastRun@".
Others parameters could be added like:
1) @JobLastRun@: UTC Datetime of last run
2) @JobStatusLastRun@: Status of last run
3) @JobNextRun@: UTC Datetime of next run
4) @JobLastBody@: Body of response of previous run3 votes
Thanks for you feedback.
It would be good to place Clone button on Scheduler Job blade like logic app for making similar jobs faster.3 votes
If you change recurrence from "Recurring" to "Once" and set a job to "Start on" past time, this job runs immediately after saving. This behavior is a little bit confusing to users who expect the job should not start. It’s very helpful if a caution appears on the portal when users are going to save jobs with past time.1 vote
- Don't see your idea?