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

GSA / notifications-api

The API powering Notify.gov

Other

10 stars 1 forks source link

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

Open heyitsmebev opened 6 months ago

heyitsmebev commented 6 months ago

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.

terrazoon commented 5 months ago

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

A-Shumway42 commented 5 months ago

@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.

ccostino commented 4 months ago

Is it possible that this is also related to this error being thrown in the API? https://github.com/GSA/notifications-api/issues/1136

Edit: It definitely appears this is related to https://github.com/GSA/notifications-admin/issues/1397 as well.

ccostino commented 3 months ago

Noting here that without these two things split, that's why we're sometimes seeing stack traces like what was noted in https://github.com/GSA/notifications-api/issues/1134.

ecayer commented 2 months ago

Moving back to up-next, because we believe this is unblocked?