Submit: Update to queueing process

[annalbrecht]

Based on info in https://github.com/US-EPA-CAMD/easey-ui/issues/6205.

During initial queueing:

• There is currently a popup indicating that queueing of a file was successful. We need to add a new message/popup for when the queueing is not successful. The error text should read: "Error: An error occurred during the file queueing process. Please try again. If you continue to encounter an error, please contact ECMPS Support."
• The submitter should be notified via email that their attempted submission was not successfully queued (example email in screenshot below).
• If part of the submission set cannot be queued, the whole submission set should fail.

Acceptance Tests When queueing fails:

• The popup box says: "Error: An error occurred during the file queueing process. Please try again. If you continue to encounter an error, please contact ECMPS Support."
• The submitter is notified via email that their submission was not successfully queued. The email should include: -- ORIS Code -- Location -- Date/Time -- Submitter -- Any applicable log information. See https://github.com/US-EPA-CAMD/easey-ui/issues/6393.

When one file in the submission set fails to queue, the whole submission set is marked as failed and an email notification is sent to the user (as described above).

[yonatan-dp]

@annalbrecht This ticket does not require that we send a separate email to ECMPS Support on queueing failure. However, ticket #6392 (for submission failures) require that we send a separate email to ECMPS Support.

1. Do we want to do that for this ticket too?
2. The requirement for the email to the user includes "Any applicable log information". This will be log information that will have very technical jargon. Just confirming that we do want to send that to the user.
3. Also, when a queuing failure occurs, some information may not be available depending on when the queuing failure occurs. In those cases, the email to the user will have as much information as available and will include the text 'N/A' for unavailable information.

[annalbrecht]

@yonatan-dp

1. Yes, send a separate email to ECMPS Support.
2. Only send the detailed log info to ECMPS Support
3. ok

[yonatan-dp]

Changes Made to Fulfill the Acceptance Criteria

The issue of inconsistent evaluation emails points to evaluation processing failures (exceptions) that are hidden from the user.

To address the issue of missing or inconsistent evaluation emails, I implemented a few changes to ensure that every evaluation— especially if unsuccessful—results in an email notification to the user and ECMPS support. Below is a summary of the modifications:

---

1. Consistent Error Handling and Email Notification Logic

• For notification of evaluation errors, I have mirrored the submission queueing notification logic in easey-ui/issues/6391. This will make notification consistent for evaluation and submission processes.
  • All-or-Nothing Queueing: If any part of the evaluation set cannot be queued, the entire evaluation set is marked as failed, triggering an error email to both the user and ECMPS support.

  • Evaluation Set Tracking: Even if certain evaluation set IDs fail to queue and do not persist in the database, these IDs will appear in the email notifications. This enables ECMPS support to correlate these IDs with entries in debug logs (traceability).

2. Ensuring Email Notification for All Failures

• Queueing Errors:
  • Queueing errors are handled within camd-services, ensuring that any issues occurring during the initial queueing of evaluation sets trigger a notification email.
• Evaluation Processing Errors:
  • A new API endpoint within camd-services is now available to handle errors that occur during evaluation processing. This endpoint can be invoked by the quartz-scheduler (which manages the evaluation process) to send error emails that occur during evaluations. POST {{baseCamdServicesUrl}}/camd-services/email/eval-error { "evaluationSetId": "b2b5f26a-5398-42d7-81b9-b61e57eb4761", "evaluationId": 456, "rootError": "Error details for testing purposes.", "queueingStages": [ { "action": "QUEUE_STARTED", "dateTime": "2024-10-31T10:00:00" }, { "action": "QUEUE_COMPLETED", "dateTime": "2024-10-31T10:05:00" } ] }

3. Example Screenshots

Sample Email to User

Sample Email to ECMPS Support

---