app/templates/partials/check/sent-previously.html

<h1 class='banner-title' data-module="track-error" data-error-type="File previously sent" data-error-label="{{ upload_id }}">
  These messages have already been sent today
</h1>
<p>
  If you need to resend them, rename the file and upload it again.
</p>
Warn if a file has been sent already We have some teams who haver a series of files they have to send each day. It’s easy to get muddled up and accidentally send the same file again, if you think you haven’t already sent it. This commit blocks you from sending the same combination of template version and filename more than once on the same day[1]. This won’t affect teams who re-use the same template to give (for example) updates on an incident for business continuity. These teams edit the template between each send, thereby updating the version number of the template. 1. This is based on how the `limit_days` argument to the API works - you can dig into the code here: https://github.com/alphagov/notifications-api/blob/2bd4f74ad0e24f7066e1a6bd4d0e515b4b925e10/app/dao/jobs_dao.py#L50 2019-02-04 14:08:11 +00:00			`<h1 class='banner-title' data-module="track-error" data-error-type="File previously sent" data-error-label="{{ upload_id }}">`
Remove ‘You’ve’ It could be someone else who’s uploaded them. 2019-02-05 15:07:19 +00:00			`These messages have already been sent today`
Warn if a file has been sent already We have some teams who haver a series of files they have to send each day. It’s easy to get muddled up and accidentally send the same file again, if you think you haven’t already sent it. This commit blocks you from sending the same combination of template version and filename more than once on the same day[1]. This won’t affect teams who re-use the same template to give (for example) updates on an incident for business continuity. These teams edit the template between each send, thereby updating the version number of the template. 1. This is based on how the `limit_days` argument to the API works - you can dig into the code here: https://github.com/alphagov/notifications-api/blob/2bd4f74ad0e24f7066e1a6bd4d0e515b4b925e10/app/dao/jobs_dao.py#L50 2019-02-04 14:08:11 +00:00			`</h1>`
			`<p>`
Refine wording of ‘already sent’ error 2019-02-05 14:59:21 +00:00			`If you need to resend them, rename the file and upload it again.`
Warn if a file has been sent already We have some teams who haver a series of files they have to send each day. It’s easy to get muddled up and accidentally send the same file again, if you think you haven’t already sent it. This commit blocks you from sending the same combination of template version and filename more than once on the same day[1]. This won’t affect teams who re-use the same template to give (for example) updates on an incident for business continuity. These teams edit the template between each send, thereby updating the version number of the template. 1. This is based on how the `limit_days` argument to the API works - you can dig into the code here: https://github.com/alphagov/notifications-api/blob/2bd4f74ad0e24f7066e1a6bd4d0e515b4b925e10/app/dao/jobs_dao.py#L50 2019-02-04 14:08:11 +00:00			`</p>`