Hi community,
My Developer / Agentforce org has gone inactive because I last logged in back in April. When I try to access it now, it is stuck in a loop showing the "Stay Tuned... We are setting things up" provisioning page and sometimes throws a "We've hit a snag" error.
Since I am within the 180-day inactivity window, my project data should still be there. Can a Salesforce community manager or support moderator please help escalate this to the backend team to manually wake up or refresh my environment?
(Note: I can provide my specific org username securely to a Salesforce employee if requested).
Thank you!
#Trailhead #Developer Edition Org #Agentforce #Trailhead Playground
Worth flagging up front: your assumption about a 180-day inactivity window doesn't match the current Developer Edition org expiration policy, which is much shorter now. Per Salesforce's official documentation, current-generation Developer Edition orgs (this explicitly includes Agentforce and Data Cloud DE orgs) that haven't been logged into for a while follow this timeline: days 1 through 14 after being flagged inactive, you can still log in and that reactivates the org; from day 15 onward, the org is permanently deleted and you can no longer log in. There is no 45-day or 180-day grace period for current DE orgs; that longer window only applies to Developer Edition (Legacy) orgs, and even there the outer limit before permanent deletion is 45 days.
Since you last logged in back in April, you are many months past even the most generous legacy window. The "Stay Tuned, we are setting things up" loop and the "We've hit a snag" error you're seeing are classic symptoms of trying to access an org that has already been expired and deleted on the backend, rather than one that's mid-reactivation and just needs a nudge. There generally isn't a manual "wake up my org" intervention available for free Developer Edition orgs once they've passed the deletion threshold, since these orgs don't carry a paid support SLA, so a community manager typically can't force-restore one from this state.
The practical path forward: create a new Developer Edition org via Browse Trials at
developer.salesforce.com. If your old org has already been deleted, its username becomes available for reuse once deletion completes, so you may be able to register a new org with the same username if that matters to you. Unfortunately, if the org is confirmed deleted, any project data in it is not recoverable.
Source: Developer Org Expiration -
https://help.salesforce.com/s/articleView?id=sf.admin_de_org_expiration.htm&language=en_US&type=5Assumption: I can't see your specific org's backend status, so I can't 100% confirm it has already been deleted versus genuinely stuck mid-provisioning. But given the timeline you described is well outside every documented reactivation window, deletion is by far the more likely explanation for the behavior you're seeing.
