Table of Contents

Class IncrementOutboxMessageAttempts

Namespace
Excalibur.Outbox.Postgres
Assembly
Excalibur.Outbox.Postgres.dll

Represents a data request to increment the attempt count of an outbox message in the Postgres database.

[NoTenantTerm(TenantConfinement.IdentityAddressed, "the post-claim mutation path: the drain has already claimed this row cross-tenant and counts an attempt against it by its globally-unique message id. This store holds no tenant context to filter by - an outbox store reads no ambient tenant context and accepts a tenant only as an explicit argument - so the statement carries no tenant term, and a caller that supplies a message id it did not obtain from a claim reaches the row behind it. Isolation on this table is established where the row is written, by stamping tenant_id")]
public sealed class IncrementOutboxMessageAttempts : DataRequest<int>, IDataRequest<IDbConnection, int>, IDataRequest
Inheritance
IncrementOutboxMessageAttempts
Implements
Inherited Members

Constructors

IncrementOutboxMessageAttempts(string, string, int, CancellationToken)

Initializes a new instance of the IncrementOutboxMessageAttempts class.

public IncrementOutboxMessageAttempts(string messageId, string outboxTableName, int sqlTimeOutSeconds, CancellationToken cancellationToken)

Parameters

messageId string

The unique identifier of the message to increment attempts for.

outboxTableName string

The name of the outbox table.

sqlTimeOutSeconds int

The SQL command timeout in seconds.

cancellationToken CancellationToken

The cancellation token.

Remarks

The update targets the globally-unique outbox message_id, which addresses exactly one row, so no tenant predicate is applied: the drain is cross-tenant infrastructure and must always be able to update the row it claimed, regardless of any ambient tenant context.

This framework request binds its fixed primitive input and output schema without runtime emit. Replacing a known parameter value is observed at execution; custom parameter metadata, templates and output callbacks are not an extension contract. Custom IDataRequest implementations are unchanged.