Issues

SQS: RejectAsync deletes the source message when the DLQ send fails — should it release instead (as spec 0037 R-19 does for GCP)?

1 - Up Next

Bug

#4415

· iancooper opened

on Sep 24, 2026

AutoFromAssemblies() registers FireSchedulerRequestHandler twice, so scheduled requests through DI throw

2 - In Progress

Bug

#4414

· iancooper opened

on Sep 24, 2026

Azure Service Bus: could a publication or a message set ServiceBusMessage.TimeToLive?

#4411

· gitmln opened

on Sep 23, 2026

Azure Service Bus: Header.PartitionKey is written only as cloudEvents:partitionkey, so ServiceBusMessage.PartitionKey is never set

#4410

· gitmln opened

on Sep 23, 2026

Scheduled Send/Publish/Post (delay or at) drop the RequestContext, so headers set through RequestContextBagNames.Headers never reach the message

#4404

· gitmln opened

on Sep 22, 2026

AutoFromAssemblies registers the built-in scheduler handlers a second time, so the first delayed Send/Publish/Post throws "More than one handler was found"

#4403

· gitmln opened

on Sep 22, 2026

Five async outbox call sites discard the ResilienceContext cancellation token, defeating the async resilience-context branch

#4393

· iancooper opened

on Sep 21, 2026

RequestContext.CreateCopy() silently drops ResilienceContext, so Publish to one observer and Publish to many take different resilience paths

#4392

· iancooper opened

on Sep 21, 2026

AWS SQS FIFO: delayed send always takes the native DelaySeconds path, which FIFO rejects — route FIFO through the Scheduler seam as SNS FIFO does

#4390

· iancooper opened

on Sep 21, 2026

rocketmq-ci has been disabled since #3696: nine RocketMQ conformance cells read Fixed but run nowhere

#4389

· iancooper opened

on Sep 21, 2026

RMQ: the native x-delayed-message path is non-conformant — a requeue delay is discarded, and delivered messages carry a non-zero Header.Delayed

#4388

· iancooper opened

on Sep 21, 2026

RMQ: no invalid-message destination is modelled, so unacceptable rejections dead-letter to the DLQ

#4387

· iancooper opened

on Sep 21, 2026

Navigation Menu

All issues

SQS: RejectAsync deletes the source message when the DLQ send fails — should it release instead (as spec 0037 R-19 does for GCP)?

AutoFromAssemblies() registers FireSchedulerRequestHandler twice, so scheduled requests through DI throw

Azure Service Bus: could a publication or a message set ServiceBusMessage.TimeToLive?

Azure Service Bus: Header.PartitionKey is written only as cloudEvents:partitionkey, so ServiceBusMessage.PartitionKey is never set

Scheduled Send/Publish/Post (delay or at) drop the RequestContext, so headers set through RequestContextBagNames.Headers never reach the message

AutoFromAssemblies registers the built-in scheduler handlers a second time, so the first delayed Send/Publish/Post throws "More than one handler was found"

Five async outbox call sites discard the ResilienceContext cancellation token, defeating the async resilience-context branch

RequestContext.CreateCopy() silently drops ResilienceContext, so Publish to one observer and Publish to many take different resilience paths

AWS SQS FIFO: delayed send always takes the native DelaySeconds path, which FIFO rejects — route FIFO through the Scheduler seam as SNS FIFO does

rocketmq-ci has been disabled since #3696: nine RocketMQ conformance cells read Fixed but run nowhere

RMQ: the native x-delayed-message path is non-conformant — a requeue delay is discarded, and delivered messages carry a non-zero Header.Delayed

RMQ: no invalid-message destination is modelled, so unacceptable rejections dead-letter to the DLQ

Search results