The biggest problem you're likely to encounter is thinking that something didn’t happen that should have. For example, an email wasn't sent or a Trigger didn't fire. The most likely explanation is that your project is experiencing the usual delays inherent in the Internet but remember too that some services may be dealing with peak volumes of activity. This means that although an email was sent from Conducttr exactly at the time specified by the Trigger, it may not arrive immediately.
Regards internal delays, whenever possible Conducttr processes Triggers immediately. However, for Twitter and YouTube, Conducttr must poll the services at regular time intervals. This will mean a change of views on a video or an incoming Tweet with the correct match phrase will be processed at the next interval.