Skip to content

Conversation

@theseanything
Copy link
Contributor

Introduces a new architectural decision record (ADR047) outlining replacing the fixed delivery_status enum with a computed status method based on delivery timestamps allowing us to make S3 submission async.

Introduces a new architectural decision record (ADR047) outlining replacing the fixed delivery_status enum with a computed status method based on delivery timestamps allowing us to make S3 submission async.
@theseanything theseanything force-pushed the theseanything/adr-for-submission-status branch from 2e37606 to 38739a3 Compare December 4, 2025 12:06
@lfdebrux
Copy link
Member

I'm not sure if it changes anything, but I thought I better flag it; in a recent support case (https://trello.com/c/1yMdH3Nk/2741-bounced-submission-emails-for-form-1693), we had bounce notifications that arrived 2.5 hours after the delivery notification, apparently due to issues with the receiving mail server. However, when asked, the form creator reported that the emails had been delivered.

What I think this means is that, for email submissions at least, the status can be more ambiguous than the status of delivered or bounced would necessarily suggest.

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.

4 participants