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

Failed Messages Folder #35

Closed
lkwirica opened this issue Feb 24, 2021 · 6 comments
Closed

Failed Messages Folder #35

lkwirica opened this issue Feb 24, 2021 · 6 comments
Assignees
Labels
duplicate This issue or pull request already exists

Comments

@lkwirica
Copy link

Generate a failed list for the HCWs to whom the messages fail to send i.e. Failed Box such as inbox, to make possible to interrogate the cause of failure e.g. rectify the contact, obtain an updated contact etc. The current failed messages are not hitting Rapid pro Failed folder

@cloehr651
Copy link

Please see the reports mock up that I requested you review. Does the Outbox and Sent tab fulfill your needs?

@cloehr651 cloehr651 added the duplicate This issue or pull request already exists label Feb 24, 2021
@lkwirica
Copy link
Author

lkwirica commented Mar 2, 2021

@cloehr651 I will review the mock up reports. However, this issue seems to relate to issue #40

@cloehr651
Copy link

@ashaban it seems like this could be displayed in the Flow Run breakdown and Message Sending Breakdown reports - in the status filter but "failed" doesn't show up as an option. Is that where you were planning to add this or as a separate report?

@njugunask
Copy link

@ally, does ‘completed’ and ‘entered in error’ mean ‘sent’ and ‘failed’ respectively in the message sending breakdown?

@ashaban
Copy link
Member

ashaban commented Jun 16, 2021 via email

@njugunask
Copy link

Thanks, Ally.
This issue needs to be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants