Large GlideRecord queries without proper limits or inefficient loops processing thousands of records without chunking or yielding control. (high likelihood)
Infinite or deep recursive function calls that consume excessive processing time before the stack limit is reached. (high likelihood)
Synchronous external HTTP calls using RESTMessage or SOAPMessage within business rules that experience network delays or timeouts. (medium likelihood)
Complex database operations or joins on large tables without proper indexing causing query performance issues. (medium likelihood)
System transaction quota set too low for legitimate long-running operations like data imports or bulk updates. (low likelihood)