Summary

• Replace try-catch approach with explicit existence check before creating BillingEmailHistory records
• Eliminates recurring constraint violation errors that appear every 15 minutes in the logs
• Maintains the same functionality of preventing duplicate billing notification emails

Problem

The application was experiencing frequent unique constraint violations on the email_history_active_workspace_type_idx index, occurring approximately every 15 minutes. These errors appeared in the logs as:

ERROR: duplicate key value violates unique constraint "email_history_active_workspace_type_idx" (SQLSTATE 23505)

The previous code attempted to create a BillingEmailHistory record and then caught the constraint violation error, but this approach still generated error logs even when the constraint violation was properly handled.

Solution

Changed the approach to:

1. First check if an active BillingEmailHistory already exists for the workspace and email type
2. Only create a new record if none exists
3. Remove the error handling for constraint violations since they won't occur anymore

This prevents the constraint violation from happening in the first place, eliminating the error logs while maintaining the same business logic.

Test plan

• Verify the application compiles successfully
• Test that billing notifications are still sent appropriately
• Confirm that duplicate billing notifications are still prevented
• Monitor logs to ensure constraint violation errors no longer appear

🤖 Generated with Claude Code