UBEs failing after cleaning Runtime Cache and Spec folders

  Hello there,

    Basically what I need to know what is the behavior of E1 when after deleting Runtime cache and spec folder we send different versions of the same UBEs through scheduler.

    I got this situation:

 We have some scheduled processes whereby multiple copies of the same UBE and version are submitted at virtually the same time by the scheduling software. We are finding that if/when we periodically clean up the RuntimeCache/UBEOverride folders as part of routine system maintenance, the first time we runt he above scheduled process, one or more of the concurrent submissions fail, while others several seconds later are successsful. We presume this is because of the way the Metadata kernel does the initial population of those folders the first time a UBE/version is run...the rdaspec/gbrspec creation of those cache folders is still