-
Notifications
You must be signed in to change notification settings - Fork 406
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
Unable to send messages after 5.5.2 update #1610
Comments
Hello @eanthonyq , Also, please share deployment status screenshots of all the Function apps and App service from the deployment center. Here is the reference for App service status. Please do the same for 3 function apps(Data Function, Send Function, Prep Function) |
Hi @v-jaygupta, I've gone back through 5.x upgrade steps.
It looks like the Function Apps were not at the same version as the Web Application. They all look to be at the same versions now.
After their restarts I confirmed in the Author Application in Teams that all organization specific configurations were displaying and configured I was able to delete messages from the Application. Resending a message to users now produces the same Orchestrator Error but there is additional Warning Information. That was not displayed before. The actual being displayed in the Warning is the App ID for the UserAppID App Setting in the Web Application and 3 Function App Environmental Variables. Errors |
Hi @eanthonyq, From the screenshot it seems like you are using a custom repository here. Can you please recheck and send screenshot of Deployment Center of any of the function app / Web app ? Please note that if you are not using Official version of the Company Communicator, it will be out of our Support Scope as per our Support Policy |
Hi @tiwariShiv7, It seems like there are 2 repository URLs being used across the Web App and 3 Function Apps. Web App and the -data-fuction are using: The -prep-function and the -function are using: When I follow the link to the Branch from the Deployment Center on any of those I am taken to the same URL: If this is not the official version could you help me with the steps to link it to the correct one? |
The correct URL is https://github.com/OfficeDev/microsoft-teams-company-communicator-app.git |
Hi @eanthonyq, can you please provide your ID to connect over Teams along with your time zone? |
Hi @tiwariShiv7, I can be reached at [email protected] and I'm on EST. |
Hi @eanthonyq We will soon start the conversation over Teams. Meanwhile request you to please update all the Function apps and web app repository URL to "https://github.com/OfficeDev/microsoft-teams-company-communicator-app.git" and perform a one time sync, Wait for 24 hrs tp reflect the changes. If it still doesn't work please let me know, I'll reach to you on Teams after this. |
Hi @tiwariShiv7 I've changed the GIT URLs for the functions to all point to the provided URL and performed resyncs. I retried sending a message through communicator after 24 hours and am still receiving the same error: Errors |
We updated to 5.5.2 on October 15th and haven't been able to send messages from the Application since.
I've reviewed Issues #1061, #1551, #1608 and #1593 and tried the steps taken in them as the errors are similar to what was referenced in them.
GraphAppId -- GraphAppPassword
AzureAd:ClientId -- AzureAd:ClientSecret
UserAppId -- UserAppPassword
AuthorAppId -- AuthorAppPassword
The errors I'm seeing in the Failures reports are 401 errors to a few API calls:
GET /api/draftnotifications/scheduledDrafts
GET /api/draftnotifications/
GET /api/sentnotifications
As well as OrchestrationFailures in the SyncRecipientsOrchestrator Function.
Example OrchestrationFailures Error:
Exception while executing function: SyncRecipientsOrchestrator Orchestrator function 'SyncRecipientsOrchestrator' failed: The activity function 'BatchRecipientsActivity' failed: "Object reference not set to an instance of an object.". See the function execution logs for additional details.
From the resolved tickets this seems to be a secret related issue, but we've checked a few times that the active secrets in the KeyVault for the App Registrations are valid.
Any guidance would be greatly appreciated.
The text was updated successfully, but these errors were encountered: