adjust user's next-outgoing extension AFTER communication request status change #78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
achen2401
approved these changes
Jan 7, 2025
|
@pbugni thank you. The fix appeared to resolve the issue that I saw. first scheduled message date/time: After that has been sent, the next scheduled message date/time displays as expected: |
mcjustin
approved these changes
Jan 7, 2025
…ng status of communication request.
…h the followup values)
…not touch the followup values)" This reverts commit 5a2de54.
pbugni
force-pushed
the
bugfix/correct-next-outgoing
branch
from
bb72bbd to
b46af32
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pivotal story: https://www.pivotaltracker.com/n/projects/2584667/stories/188742640
next-outgoing was incorrect after message send.
the code order was in error - the attempt to update the user's extension for "date-time-of-next-outgoing-message" happened prior to the communication request status change on message send.
This PR depends on uwcirg/isacc-environments#40 (or the migrations won't run correctly)