Skip to content

fix(registration): preserve Outlook batch task mailboxes#92

Open
GRD-Chang wants to merge 2 commits intodou-jiang:mainfrom
GRD-Chang:fix/outlook-batch-mailbox-binding
Open

fix(registration): preserve Outlook batch task mailboxes#92
GRD-Chang wants to merge 2 commits intodou-jiang:mainfrom
GRD-Chang:fix/outlook-batch-mailbox-binding

Conversation

@GRD-Chang
Copy link
Copy Markdown

Summary

This PR fixes Outlook batch registration so each task keeps using its own bound mailbox instead of falling back to the batch-level mailbox configuration.

Changes

  • restore Outlook batch scheduling coverage for task creation and execution
  • resolve email_service_id from the registration task before running batch jobs
  • fall back to the task-bound mailbox inside the sync registration worker when needed
  • add regression tests for Outlook batch mailbox binding

Verification

  • .venv/bin/python -m pytest -q tests/test_outlook_batch_registration.py tests/test_registration_new_api.py
  • 7 passed in 1.00s

Notes

  • testing was done without triggering real registrations
  • PR scope is limited to batch registration mailbox binding behavior

Pass registration_type through the Outlook batch runner so the background task signature matches the scheduled arguments.

Add regression coverage for scheduling and batch dispatch without including unrelated workspace artifacts.
Use each registration task's bound email_service_id during batch runs instead of falling back to the batch-level mailbox configuration.

This keeps Outlook batch registration aligned with the user-selected inboxes in both parallel and pipeline execution paths, and adds regression coverage for task-bound mailbox resolution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant