I'm wondering if someone has a best practice / blueprint which works better than the following scenario that I've got myself into:

  1. Created a managed package in a D.E. org which contains a Flow
  2. Deployed managed beta to Test Org
  3. Attempted to delete managed beta so I can install new version of beta
  4. Cannot for 12 hours. Why? Well, the Flow must be i) deactivated then ii) must wait 12 hours to delete a flow then iii) I can finally delete the managed package to iv) finally update the managed beta

As such, I removed the Flow from the managed package and I now deploy Flows manually from Eclipse IDE to Test Org after the managed beta package.

PROBLEM: The Flow works fine in the DE Org where the managed package is first created. It can reference custom objects like this "ObjectName__c". But when the Flow is deployed into the Test Org with the managed package, it no longer "sees" any objects until I manually go into the XML (in Eclipse IDE) and modify all field, Apex CLass and Object references to "Namespace__ObjectName__c", then redeploy the Flow to the Test Org.

FURTHER PROBLEM: When I try to save the Flow to the DE Org ("save to server") using the IDE (where the managed package is originally created), the IDE automatically removes all the "Namespace__" prefixes I just hand entered. To be clear -- I did not "refresh from server", but rather "save to server" and it seems to happily modify all the *.flow contents on my behalf.

I know I must be making a newbie mistake somewhere and there's gotta be a better way than waiting 12 hours between Test Org updates.


1 Answer 1


Indeed an interesting problem, I was not aware Flows deactivation and deletion had this requirement, seems strange. However sure enough it is documented, though the reasoning still seems weak, especially considering, unlike Workflow, there is no scheduled aspect to Flow.

You can’t delete an active flow. Once deactivated, you must wait 12 hours to delete a flow or flow version. This ensures that flows in progress have time to complete. Flows that have never been activated can be deleted immediately.

If I am understanding correctly here, I am assuming you still desire to include it in your package eventually, just not during the Beta package testing phase. During this time you obviously want to be able to develop your Flow, ideally in place where the namespace qualifications are maintained. So you don't have to keep re-editing your file each time you pass it over for testing with your Beta package.

Some thoughts then...

  1. Move to Release Package Early. If you are in the part of your development cycle where you are confident about the Custom Objects and global Apex classes in your release. There really is not much to be lost by going to Release package. In this case a lot to be gained, since you can then upgrade your package and thus the flow. This would allow you to put the flow back in your package. It might sound a bit strange, but for the sake of a few minor version increments as you make your final revs to the package ahead of release, moving to Release status during your Beta phase can often help a lot.
  2. Multiple DE Test Orgs. You could create a set of DE orgs and cycle them around depending on the age of the Flows you need to delete. Depending on how often your doing releases, maybe 3 or 4 would get your between days. This would allow you to put the Flow back in the package and avoid your editing problem. Downside is it harder to manage with the testers, as they need to know which of your 4 test orgs your using at the time.
  3. Designate a DE org with "a" version of your Beta in. Depending on how much the aspects of your package on which your Flow depends apone are changing. You could consider doing your Flow editing in separate org with a fixed version of your Beta in. This is obviously less ideal if things are changing in the package the Flow needs. As I'm not sure of this, thought I'd through this consideration in. In this case the namespaces will not be removed when you save.
  4. Eclipse RegEx Find/Replace / Script. If you want to take a bit of sting out of the editing process, it's worth taking a look at the Regular Expression support in Eclipse's Find/Replace dialogue. I've used this effectively in the past for such things, and once you've nailed the RegEx its a few seconds to run it, then copy paste it over to your Beta test package. Even if you get it working partially with a few manual edits it may still save some time.

Thats about it for ideas. Speaking of which I would raise this Flow Dev Life Cycle issue on Ideas, its far from ideal and I am sure it's something that could be addressed easily. Even if for example the platform would say bypass the 12hr wait for Flows that it knows are from a Beta package.

Hope this helps.

  • 1
    I like #4 with a dash of #3, because the issue with #1 is I'm not ready and #2 has the issue of sample/test/demo data created in one not existing in others (constant data replication/sync issues). I will made an entry in Ideas as well...
    – Emilio
    Mar 9, 2013 at 17:51
  • Since one of your comments had to do with making a mistake somewhere I believe the answer is "no you are not". The 12 hrs stinks and creates a mess but there isn't a good solution I've seen.
    – ddeve
    Mar 9, 2013 at 18:53
  • Sounds like a nice drink Emilio! Glad this help a little. Mar 9, 2013 at 23:49

You must log in to answer this question.

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