CRM fulfillment experienced an error during the processing of an email (rollback segment problem). Restarting the email caused a runaway cpu-intensive session even though the email was subsequently cancelled.

Cause of runaway session: user created content using the wrong content type (admission content type instead of campus email), which relied on admission data being in the system.

Resolution: We bounced the application server and killed the runaway session. User recreated email with correct content type.