batch emails now check for action types

[JadeCara]

Ticket ENG-2467

Description Of Changes

When consent DSRs run they still check all of the erasure email connection configs which can cause errors unrelated to consent requests.

Additionally if a consent request has multiple rules ie consent and erasure it will only send the erasure email regardless of how the config/toggles are set.

Code Changes

• src/fides/api/service/connectors/base_erasure_email_connector.py - removes artificial restriction from erasure emails
• src/fides/api/service/request_runner_service.py - Optimized needs_batch_email_send() to only check connectors relevant to the policy's action types
• test_request_runner_service.py - Added regression test to prevent future issues

Steps to Confirm

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Jan 29, 2026 8:21pm
fides-privacy-center	Ignored		Jan 29, 2026 8:21pm

[greptile-apps]

Greptile Overview

Greptile Summary

Fixed a bug where consent/erasure DSRs were checking all email connectors regardless of policy action types, which caused errors when irrelevant connectors were misconfigured. The needs_batch_email_send() function now filters connectors based on the policy's action types:

• Consent-only policies now only check consent email connectors
• Erasure-only policies now only check erasure email connectors
• Policies with multiple action types check all relevant connector types

The fix includes a comprehensive regression test that verifies misconfigured connectors of the wrong type don't cause errors.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are well-scoped, logically sound, and include comprehensive test coverage. The optimization prevents unnecessary connector checks and eliminates a class of configuration errors.
• No files require special attention

Important Files Changed

Filename	Overview
src/fides/api/service/privacy_request/request_runner_service.py	Optimized to only check email connectors matching policy action types
tests/ops/service/privacy_request/test_request_runner_service.py	Added regression test to verify policies only check relevant connectors

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[JadeCara]

@greptile please review

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[erosselli]

if this is going into the release, update the changelog.md directly :) since it's already been created