Skip to content

Conversation

@jeremydmiller
Copy link
Member

@jeremydmiller jeremydmiller commented Feb 9, 2026

Summary

Tests added

  1. all_tenant_durability_agents_are_started — verifies 3 durability agents start (main + 2 tenants)
  2. scheduled_message_for_tenant_is_processed — schedules a message for a specific tenant and confirms it is handled with the correct TenantId
  3. scheduled_messages_for_all_tenants_are_processed — schedules messages for both tenants and the main database, confirms all are processed correctly

Test plan

  • All 3 new tests pass (dotnet test --filter "multi_tenant_durability_agents")
  • All existing multi-tenancy tests still pass (dotnet test --filter "MultiTenancy")

Closes GH-2085

🤖 Generated with Claude Code -- with clean up by @jeremydmiller too!

jeremydmiller and others added 2 commits February 9, 2026 07:53
Verify that scheduled messages and durability agents work correctly for
non-master tenant databases in multi-tenant PostgreSQL setups.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

Scheduled messages and DLQ replays not processed for non-master tenants in PostgreSQL multi-tenancy

1 participant