Cannon Smith: > We just released a new version of our software a week and a half ago. In this > version I added a palette window on the server which runs On Timer. I also > added code to most every background process which updates some information > every time it wakes up from a Delay Process call. The palette window checks > this information and, if it sees a process that has been asleep longer than > one minute, resumes the process and sends us a Slack message identifying the > server and process that was asleep. If the process does not get resumed, > another Slack message is sent so we can handle the issue manually before our > customer knows. > > Interestingly, this mechanism was triggered on Sunday morning at 1:01 AM for > 9 servers. All 9 reported one or more stalled processes within a 60 second > time period.
I also have a palette window that runs On Timer. So the workaround for the Delay Process bug was quite simple over here. I replaced Delay Process with Pause Process (which is what Delay Process does anyway when the bug bites). In On Timer I call Resume Process. Never had any problems since I did it that way. (Still this is only a workaround and the bug should of course be fixed by 4D. Until it is fixed Delay Process is a command that should be avoided.) Greetings from Germany, Bernd Fröhlich ********************************************************************** 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] **********************************************************************
