Workflow causes Email-to-Case not creating a Case

Common Causes

The case is not being created because the field update on the Workflow Rule or Approval Process is doing one of the following:

• Blanking out a required field on the Case record.
• Updating a formatted field (such as an email field) with an incorrectly formatted value.
• Copying a value into a field that exceeds that field's maximum character limit.
• Triggering another automation (Flow, Process Builder, or Apex) that conflicts with case creation.

How to Diagnose Using Debug Logs

Use Debug Logs to identify the exact field update causing the error:

1. Go to Setup > Debug Logs.
2. Add a monitored user (the user whose context Email-to-Case runs in, typically the org's system user or the routing address owner).
3. Send a test email to the Email-to-Case routing address.
4. Review the generated debug log and search for "CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY" to identify the specific field update.

Fix: Field Length Control

If the issue is a field update that copies content without length limits:

• • Update the field update formula to control the length. For example, use LEFT(Body, 40) to copy only the first 40 characters from the Body field. This ensures the copied value does not exceed the target field's character limit.