Skip to content

[WIP] LG-15000: Send "please call" email for all remote idv flows#11596

Closed
matthinz wants to merge 5 commits intomainfrom
matthinz/15000-idv-please-call
Closed

[WIP] LG-15000: Send "please call" email for all remote idv flows#11596
matthinz wants to merge 5 commits intomainfrom
matthinz/15000-idv-please-call

Conversation

@matthinz
Copy link
Contributor

@matthinz matthinz commented Dec 4, 2024

🎫 Ticket

Link to the relevant ticket:
LG-15000

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

** is there to support backwards compat with in_person_please_call, can be cleaned up later

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This alias can be cleaned up after deploy

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a minor 50/50 state risk here--if the 50/50 state persists longer than the deliver_later delay (1 hour), it's possible that an old server could pick up the job and call idv_please_call, which won't exist. However:

  • I'm only 99% sure that's how deliver_later works here (i.e. that it re-calls the mailer method later on)
  • A 50/50 state lasting that long shouldn't happen.

I can remove this and do it in a separate deploy if folks want.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to wrap my head around this one. Is there any danger if we discover and issue and need to revert and go from new back to old?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a good callout. I hadn't considered reverting. I think this ends up looking a lot like adding a new job: deliver_later schedules a job that invokes a method on the mailer. If the mailer the job has when it runs does not have the method defined, it will fail.

So I think this will be two PRs / deploys:

  1. Add new method with IPP variant as an alias
  2. Start calling it for remote unsupervised + update IPP to call it as well, remove alias

- Change to idv_please_call to indicate it is used by idv generally
- Keep in_person_please_call as an alias on the theory that we need it for 1 deploy
There is a minor 50/50 risk here if the 50/50 state lasts an hour or more, but that is very unlikely to happen.
@matthinz matthinz force-pushed the matthinz/15000-idv-please-call branch from 8c0601f to 3e492e8 Compare December 5, 2024 06:30
@matthinz matthinz closed this Dec 5, 2024
@matthinz
Copy link
Contributor Author

matthinz commented Dec 6, 2024

Gonna split this across a couple PRs / deploys. First one is #11604

@matthinz matthinz deleted the matthinz/15000-idv-please-call branch December 6, 2024 19:56
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.

2 participants