Skip to content

fix(message): distinguish queued delivery state - #38

Merged
Neup123 merged 1 commit into
mainfrom
fix/queued-delivery-state
Sep 23, 2026
Merged

Neup123 merged 1 commit into
mainfrom
fix/queued-delivery-state

Conversation

@Neup123

@Neup123 Neup123 commented Sep 23, 2026

Copy link
Copy Markdown
Owner

Fixes #37\n\n- Marks enqueue acceptance explicitly as not sent: accepted=true, messageWasSent=false, deliveryStatus=PENDING, final=false.\n- Re-resolves the current template and rechecks all safety rules before each actual attempt.\n- Requeues a temporary block only when its new schedule remains within the configured queue horizon.\n- Marks long waits and permanent policy rejections FAILED with diagnostic policy reasons.\n- Updates OpenAPI, docs, unit tests, PostgreSQL tests, and bumps to 5.5.2.\n\nVerified with queue/safety tests, lint, build, and runtime OpenAPI audits.

@Neup123
Neup123 merged commit ddc6e9c into main Sep 23, 2026
4 checks passed
@Neup123
Neup123 deleted the fix/queued-delivery-state branch September 23, 2026 13:43
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.

Queued send responses and delivery-time policy outcomes are ambiguous

1 participant