Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When a message is scheduled, personalization cannot be retrieved by using Jobs or Notifications API #912

Open
heyitsmebev opened this issue Apr 10, 2024 · 2 comments
Assignees

Comments

@heyitsmebev
Copy link

When a user schedules a message, the confirmation status page is unable to display a preview of the message due to the absence of associated personalization. It appears that a notification_id is not generated and stored in the Jobs table until the message is sent. Personalization seems linked solely to the Notifications table and not to Jobs. As a result, when a message is scheduled, there is no personalization available for retrieval.

Image

@heyitsmebev heyitsmebev changed the title When a message is schedule, personalization cannot be retrieved by using Jobs or Notifications API When a message is scheduled, personalization cannot be retrieved by using Jobs or Notifications API Apr 10, 2024
@VRagulina VRagulina transferred this issue from GSA/notifications-admin Apr 10, 2024
@terrazoon
Copy link
Contributor

@A-Shumway42 is this the same issue we had before? Where we needed to separate 'create job' and 'start job'?

@A-Shumway42
Copy link
Member

@terrazoon Yeah, I believe this connected. Both this issue and the calculation of the message parts with personalization to show users could be taken care of if we separate those processes.

@anagradova anagradova self-assigned this May 9, 2024
@anagradova anagradova removed their assignment May 10, 2024
@terrazoon terrazoon assigned terrazoon and A-Shumway42 and unassigned terrazoon May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗 In progress (WIP: ≤ 3 per person)
Development

No branches or pull requests

4 participants