CODEWITHSUNDEEP
azureazure-webjobsazure-webjobssdk
MichaelLo
MichaelLo

Reputation: 1319

Azure WebJob Schedule Error - ETAG

Trying to publish a webjob from Visual Studio 2013, but I'm getting the following error in the output window:

Error   14  An error occurred while creating the WebJob schedule: BadRequest: The condition specified by the ETag is not satisfied.

The job is being published as an "on demand" type instead of "scheduled".

Ideas?

enter image description here

Upvotes: 2

Views: 1154

Answers (4)

Nagoh
Nagoh

Reputation: 813

Not sure if it has much to do with this, but I was experiencing the same issue for a Webjob being published in the Australia East region.

I was trying to publish a scheduled job, but was getting the error:

Error 14 An error occurred while creating the WebJob schedule: BadRequest: The condition specified by the ETag is not satisfied.

I did notice some restrictions on the webjobs in the free tier (see here - http://azure.microsoft.com/en-us/documentation/articles/azure-subscription-service-limits/ )

While it doesn't say that scheduled jobs were excluded from the free tier I had suspicions it would have been (it makes sense for scheduled to be excluded from this tier from a MS point of view).

To fix, I simply changed the website tier to Standard, and I've been able to successfully deploy my job.

Hope that helps someone.

Upvotes: 0

Maria Ines Parnisari
Maria Ines Parnisari

Reputation: 17506

The following screenshot taken from the Azure Portal shows the regions that can be used to create scheduled jobs:

Regions

Upvotes: 0

MichaelLo
MichaelLo

Reputation: 1319

Redeploy the Web Site into a different region, it seems the region EAST-US2 does not support WebJobs. I deployed it into South Central Us and it works fine there.

enter image description here

enter image description here

Upvotes: 1

brady gaster
brady gaster

Reputation: 1506

I'm one of the program managers on the product and this feature in VS is important to me so I'd like to help you work through this. Any chance, is your code available so we could attempt a repro of the error you're seeing?

Upvotes: 1

Related Questions