Justin, Yeah, after I responded to you I read Miyako's comment - and your reply. It's an incredibly frustrating place to be when you do everything right and the wrong thing still happens. Unlucky.
I bet the bug is actually someplace else and is manifesting in this DELAY PROCESS bit. Which doesn't help you find it at the moment, though. Is the method running this process one of those big, complicated, gnarly types with all sorts of convoluted branchings and calls to numerous plugins and dependencies on lots of IP vars? On Mon, Jun 18, 2018 at 12:18 AM Justin Carr via 4D_Tech < [email protected]> wrote: > On 18 Jun 2018, at 4:39 pm, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > > > Justin, > > I do use DELAY PROCESS but as I said it's only for a minute or two. > > And like I said maybe I've simply been lucky. As my business mentor used > to > > say, "sometimes it's better to be lucky than smart." > > > > Hi Kirk > > We are only delaying for 10 seconds but our users were still experiencing > this problem from time to time. We have worked around it now using a method > similar to those already posted on this thread but it would sure be nice to > once again be able to trust a delayed process to wake up when it's supposed > to! > -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
