There are a few relevant Ideas. One way to maybe make salesforce fix this issue is to vote for them.
Even though this was supposed to be available in 2013 its 2017 and I still see messages that say my changeset will not be avaiavle for up to 30 minutes.
This says it was done. But it wasnt. Or at least not that I have seen. https://success.salesforce.com/apex/ideaView?id=08730000000IyYKAA0
- The above Idea also references Make change set upload real time. The Idea detail says it was delivered in 2013, but perhaps they broke it again since.
Change Set Unavailable
This change set is not currently available. Recently uploaded change sets may take up to 30 minutes to be available for deployment. Please wait 30 minutes and try deploying your change set again.
The above pretty much says it all. "30 minutes" is an outrageous time to wait to deploy code. Currently you can an email when the set has been pushed to the org, but this email that says "hey, it's ready" isn't really the reality of it. If you follow that email and go to try and deploy, you still need to wait a few minutes. This makes Eclipse still faster at deploying code, by leaps and bounds, but Change Sets are better for grouping objects to deploy, so there's no real winner.
- There's another idea requesting that the mail is send only when it's actually ready: Deploy: Outbound change sets: Please send notification email when deployment IS
#Deploy: Outbound change sets: Please send notification email when deployment IS
When using the outbound change set tool to send updates to our production org we recieve an email notification when the change set is uploaded. This is useless information since it fools you to think that you can deploy the objects.
If you click on the "change sets awaiting deployments"-link you will get a "CHANGE SET UNAVAILABLE" message.
It even says in your helptext that the uploaded material could be unavailble up to 30 minutes.
>> Please send the notification email to be sent when it IS available for deploment. <<
And... thank your for providing this functionality since this is a really nice way of moving objects/code from the sandbox to any other organization. =)
