Catching problems related to asynchrononous updates

Nov 15, 2010 at 3:42 PM

The documentation says, "Be aware that the asynchronous mechanisms of SP2010 can make the process start on the next step before the last one is 100% complete".   I am using version 1 of SharePoint Site Configurator with Moss, I assume that is also affected by asynchronouse issues. How worried should I be about this? Are there certain SharePoint artifacts that are more likely to cause asynchronouse related problems? Is there anything I can do to limit the likelihood of encountering such problems? Is there anyway to catch and handle problems related to asynchronousism?