Does anyone have any good tips on what to look for when a a published workflow project pegs the CPU at 100% via the w3wp process the majority of the time (it will dip now and then to almost nothing for about 10 seconds then go back up to 100)? I ensured debugging was off for all the published projects and the logging configuration is only set to 'Error' for everything. The published project that is doing this has a couple of wait components (Change Control workflow gathering all approvals and tester request infobefore continuing) and alot of variables throughout. Any suggestions would be highly appreciated. Thanks