OfficeDev/microsoft-teams-apps-icebreaker

Despite "Pause matches" activated user account is proposed to others

Sem149 opened this issue · 27 comments

Issue Description

  1. User activated "Pause matches" and also does not receive notification
  2. However this user is still matched to other colleagues and therefore contacted by them

Is there any way how to disable the matching of colleagues with "pause matches" activates?

Hi @Sem149 ,
Thanks for raising the query. We will get back to you with proper response soon.

Hi @Sem149 ,
If not done previously, please try this procedure.

  1. Go to Azure Portal--> Open the resource groups-->Select the resource group where the app has been deployed-->Select logic app--> Run the trigger. Then in the UI It's time for a match! template should appear. Below is the reference.

image

image

  1. Pause all matches

image

  1. Once after pausing. Below is the response is expected from the bot. Your response was sent to the app should be coming up.

image

  1. Repeat the first step again. Now you should not be getting the It's time for a match! template. If this scenario works, pause matches is working fine.

Please let us know how it goes.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@gsv022 - did you have any chance to view and analyse our error message?

@Sem149 , Could you please share the app service logs. Here is the reference.
image

As the message is in encrypted state, not able to view the content. Please send the response here directly.

@Sai Venkat we are not able to retrieve this. Only the following is available:
image

@Sem149 , Could you please share the app service logs. Here is the reference. image

@Sem149 , Please follow the below steps.

  • Go to Azure Portal
  • Open the Resource group where Icebreaker has been deployed
  • Click on App service(web app)
  • Select Deployment center under deployment section
  • Go to logs section
  • Click on commit id
  • Copy the deployment logs and paste it in some text file and share it

Thanks for sharing the details. We will go through the above files and will get back to you.

@Sem149 , Could you please share the outlook id so that we can discuss the issue internally.

@Sem149 , Could you please mail id so that we can discuss the issue internally.

@Sem149 - Can you please share your e-mail Id (preferably Microsoft Teams E-mail Id) so that we can discuss the issue over call.

Please provide the email-id so that we can discuss the issue internally

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@Sem149 We understand that you are feeling stuck with the current situation. To better understand the issue, we would need to connect with you over a call. The email ID you shared above is getting encrypted because you are replying to GitHub via email, which makes it difficult for us to see the ID. The logs you shared don't provide much information about the issue. It would be helpful if you could share the email ID without encryption or take a screenshot of the email ID to avoid encryption.

We appreciate your patience and cooperation throughout this process.

image

@Sem149 , Could you please let us know the status

Dear both @v-royavinash @gsv022 @v-jaygupta , my mail ID is sebastian.m.mueller@allianz.de.
But before scheduling a meeting please at least give me at least a few findings. We have 2 1/2 months of going back and forth and not even one idea of what could cause the issue :-(

As I am not the affected user I will not be able to give you lot of insights.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Thanks for the update, We are closing out the issue. Please log a new issue if any issue faced with respect to Icebreaker. We are happy to assist you.

image