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

Query - User's are missing in CC send delivery report | refer issues/1579 #1628

Open
SachinWandale111 opened this issue Dec 17, 2024 · 6 comments

Comments

@SachinWandale111
Copy link

SachinWandale111 commented Dec 17, 2024

This is regarding to user's are missing in CC send delivery report refer issues/1579
As we have already performed the work around shared by you and run the below query successfully for all user's whom the message did not getting delivered.
We found that the provided work around worked for very first company communicator dispatch after sent message again to all user's whom message were not delivered earlier and they able to able to receive the new message successfully.
But after each subsequent new dispatch, we observed that again there is shortfall of user's whom the message is did not getting delivered and the count is getting increase in each new send delivery report.
We analyze the send delivery report, and observed that, Before we implement the workaround shared by you the total number of users whom message were did not delivered count was 1037.
But when we compare Nov and Dec month send delivery reports we observed there are total 306 user missing in Nov month and 374 users missing in Dec month report (Message did not delivered users).
Then again we compare 1037 users (initial count before implement the workaround) with latest Dec month send delivery report and observed that there are 318 users are common in both the report whom message did not delivered.

Please clarify below details:
i) We already performed the fix to the all missing user still why still issue again appeared for 318 users? Please clarify the reasons.
ii) Can you confirm, is there is any permanent fix for this problem?
iii) If no permanent solution then does it mean we need to perform this activity regularly before each new dispatch? As this will be time consuming.
If you requires any more details please do let me know. Thanks

Refer below earlier case:
#1579
And the Query: PartitionKey eq 'UserData' and RowKey eq 'UserId' or RowKey eq 'UserId

image
@v-jaygupta
Copy link
Collaborator

@SachinWandale111 ,
Thanks for reaching out to us!
We will check on the above queries and get back to you with proper response soon.

@SachinWandale111
Copy link
Author

Thanks for your response.

@SachinWandale111
Copy link
Author

Hello @v-jaygupta ,
Do we have any further updates on above queries please?

@v-jaygupta
Copy link
Collaborator

Hello @SachinWandale111 ,

  1. We are not sure of the reasons for now, could you please help us with the message sent logs from application insights so that we can check the failure reasons. Also, could you please checked and compare the app setup and permission policy assigned to the users who are getting receiving the message vs those aren't receiving the message.
  2. Currently, this is the only workaround in place to overcome the issue, we have a backlog item created for this which will be worked upon in future sprints.
  3. It would be better to perform this activity before sending the message to ensure there are no further failures as seens historically in your case for the month of Nov and Dec.

@SachinWandale111
Copy link
Author

SachinWandale111 commented Dec 25, 2024

Hi @v-jaygupta,
Thanks for providing your feedback.
i) Please share the details step by step process to download application insight logs.
ii) Regarding to "could you please checked and compare the app setup and permission policy assigned to the users who are getting receiving the message vs those aren't receiving the message" ===> We already checked the App setup as well as app permission policies in both the cases and they are already assigned the company communicator user policy. There is no difference in policy assignment in both cases.

@v-milibiswas
Copy link
Collaborator

Hello @SachinWandale111,
Regarding the step to go to application insights and share the logs, please follow the below steps:
Go to resource group where CC app is deployed--> Go to Application Insight resource type --> Under Investigate --> Click on failures --> share the screenshot and stack trace for top 3 response codes.
You need to share the stack trace and error screenshot by following the below suggested operation.
Here is the reference:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants