Today I had to spin some new DE orgs via the Environment Hub. I've done this often before and I thought to know the process.

But I was shocked after taken a closer look on the orgs, which have been provisioned by Salesforce as you can see here:

enter image description here

I highlighted the last known-good line green. Status was Free and Org Expiration Date was empty. Fine! That's what we need.

But now watch the red line: Status seems to be Trial and Org Expiration Date is 2017. This will result into the loss of several man-years of development-work at the time the org will expire. At this time my only explanation is, that this could be a bug in Salesforces' spinning procedure or org-template. I can't imagine that this behavior is on purpose or does make sense in any way.

I created the orgs below the red line exactly the same as I've done with the orgs above the green line. See here:

enter image description here

Reviewing Environment Hub developer edition differences I think how I fill in this form was and still is the intended way it should be done, right?


Did anyone else has witnessed this behavior, too? Does anyone know the steps to take to restore the previous behavior? Has anyone contacted the Salesforce Support on that matter and if so, how was the response?

I'm asking here because logging a ticket requires a lot time for babysitting of the case, the support reps usually try to call me and I'm not available by phone. Also it helps a lot if you can tell the support-guys exactly what you want them to do (i. e. to tell them the solution and prevent them from doing time-consuming researches with open outcome and verbose communication-ping-pong)

So any hint (as small it might be) would help me a lot to understand what is going on here an which steps I need to take.

  • In parallel I've opened a case (14137609) at the support.
    – Uwe Heim
    Commented Jul 5, 2016 at 10:17
  • Maybe the most interesting question is: am I the only one with this behavior? Can anyone reproduce it? Can anyone still create PDEs without expiration date? If I'm the only one, sure the problem is related to my Hub-Org. I can't really test this, since that Org is the only one with Environment Hub installed to which I have access to.
    – Uwe Heim
    Commented Jul 5, 2016 at 20:06
  • I confirm that behaviour. Today created PDE has expiration date set to 7/7/2017. prntscr.com/bphqid Commented Jul 6, 2016 at 12:43
  • Thanks @DenisPereverzev - now that we know it's not a one-time-occurrence, we have to hope, that someone from Salesforce will start working on case 14137609 and help us to go back to normal again. This is a very serious bug IMO. If others are going to raise own cases, please refer to my case number to combine the momentum.
    – Uwe Heim
    Commented Jul 6, 2016 at 13:50
  • 2
    @Basti only that I have logged a ticket and support fixed it. It was a simple bug I suppose. Did not repeat since than, and we are creating lots of Orgs frequently.
    – Uwe Heim
    Commented Oct 13, 2017 at 17:43

1 Answer 1


July 2020 update: the DE orgs spin up as expected from the Env Hub. Listed as Free with no expiry date.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .