-
Notifications
You must be signed in to change notification settings - Fork 407
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
Comments
@SachinWandale111 , |
Thanks for your response. |
Hello @v-jaygupta , |
Hello @SachinWandale111 ,
|
Hi @v-jaygupta, |
Hello @SachinWandale111, |
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
The text was updated successfully, but these errors were encountered: