-
Notifications
You must be signed in to change notification settings - Fork 39
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
Recipients not syncing after secret expired #76
Comments
Hi @ostromecko, could you please share the function execution logs? The Log Stream is a feature in Azure that allows you to view the live logging information directly in the Azure portal. Here’s how you can use it:
Once you’re in the Log Stream, you should start seeing logs as your functions execute. If you don’t see any logs, make sure your function app is running and executing functions. |
Hi @luishdemetrio, which function from the three functions I should open and check if there are logs? Data-Function, Function or Prep-function? |
Hi @luishdemetrio, can you please support me with the check if the functions are executed? |
@luishdemetrio I have opened Log stream, but it's constantly loading and not showing anything. Can you please support on this? |
@cristianoag could you help me with this issue? |
When you renew the secrets in KeyVault you need to make sure the configuration variables are referencing the new key. Can you check all functions and the app service and make sure they are pointing to the right place?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: ostromecko ***@***.***>
Sent: Friday, March 22, 2024 10:04:20 AM
To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Recipients not syncing after secret expired (Issue #76)
@cristianoag<https://github.com/cristianoag> could you help me with this issue?
—
Reply to this email directly, view it on GitHub<#76 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKUCYOTFEO6MU764U63YZQT5JAVCNFSM6AAAAABDIIG4FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGA3DCNRTGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Currently I'm facing this issue: |
Are you using a standard CSV file as input? Can you post it so I can check the format?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: ostromecko ***@***.***>
Sent: Friday, March 22, 2024 10:21:24 AM
To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Recipients not syncing after secret expired (Issue #76)
Currently I'm facing this issue:
Failed to prepare the message for sending:The orchestrator function 'SyncRecipientsOrchestrator' failed: "The activity function 'SyncCSVActivity' failed: "Specified argument was out of the range of valid values. (Parameter 'partitionCount') Actual value was .". See the function execution logs for additional details.". See the function execution logs for additional details.
—
Reply to this email directly, view it on GitHub<#76 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKVY4IRC2UKCLUZSWN3YZQV5JAVCNFSM6AAAAABDIIG4FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGA4DQOJXGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
of course. I'm attaching file which I'm using. |
I've just tested, and the format you provided appears to be in order and is being recognized. I suggest considering a few potential areas for investigation. Verify if all functions are correctly configured to access the appropriate keys in KeyVault. Assuming you've already done this, another possibility could be discrepancies between the versions of functions being run compared to the version of the app service. It's essential to ensure that all resources are synchronized to the same version. I recommend checking the synchronization log file for any errors or inconsistencies. |
I have checked all three functions and app service. All four instances are pointing to the same commit ID 9d9ce88. |
Do you have email addresses different than upns?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: ostromecko ***@***.***>
Sent: Friday, March 22, 2024 12:10:11 PM
To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Recipients not syncing after secret expired (Issue #76)
I have checked all three functions and app service. All four instances are pointing to the same commit ID 9d9ce88<9d9ce88>.
—
Reply to this email directly, view it on GitHub<#76 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKVHVCN3I4UVZURZ5ZDYZRCVHAVCNFSM6AAAAABDIIG4FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGMYDQNJXGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
No. I was even testing this with a file which was containing only two email address (mine, and my colleague) and still it was not working |
Email address or UPN? Very important, the file needs to have upns, not emails.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: ostromecko ***@***.***>
Sent: Friday, March 22, 2024 12:22:53 PM
To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Recipients not syncing after secret expired (Issue #76)
No. I was even testing this with a file which was containing only two email address (mine, and my colleague) and still it was not working
—
Reply to this email directly, view it on GitHub<#76 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKUBSP2HJKLGUFVARW3YZREE3AVCNFSM6AAAAABDIIG4FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGMZTIMBTHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
UPN matches e-mail address in our case. |
Collect and upload the function log files. So we can check what is going on. Need more detailed error mess
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: ostromecko ***@***.***>
Sent: Friday, March 22, 2024 12:32:54 PM
To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Recipients not syncing after secret expired (Issue #76)
UPN matches e-mail address in our case.
—
Reply to this email directly, view it on GitHub<#76 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKUAOYGS2QNWZBIRZ43YZRFKNAVCNFSM6AAAAABDIIG4FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGM2TEMRTGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@cristianoag Im facing the same problem, all my secrets has expired, you have any script to do the secrets update to the keyvault? "Permissions required. Ask your IT administrator to enable this option for you" Im assuming this message is becouse of the expired secredts that don allow access to groups/users of m365 |
Hi, I'm running the latest master version v5.31. Recently our secrets have expired, and what we did is that we generated new ones, and update them in key vault. Currently I'm receiving below error when trying to send a test message using a CSV file:
Failed to prepare the message for sending:The orchestrator function 'SyncRecipientsOrchestrator' failed: "The activity function 'SyncCSVActivity' failed: "Specified argument was out of the range of valid values. (Parameter 'partitionCount') Actual value was .". See the function execution logs for additional details.". See the function execution logs for additional details.
So I would need help with resolving this, and checking if I did not miss any secret update anywhere in the configuration.
The text was updated successfully, but these errors were encountered: