We have integrated MS Teams with Azure DevOps using below:
https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
Pipelines have been subscribed to send notifications on failure. However they stop working randomly. We are unable to identify where the problem is. Could someone guide me on how to troubleshoot the issue?
Here is a troubleshoot advice:
Please go to your Project Settings -> General/Service hooks and check the sevice hook to Microsoft Teams.
If you find that the notification was failed to send, it will usually provide an error message for further investigation.
If you find that it doesn't send notifications when the pipeline fails, it is recommended to check your connection settings. And identify the scope of the problem, such as whether this problem is related to a particular pipeline.
If you find that the notification has been successfully sent but the Microsoft Teams have not received it, you can further check if the intermittent problem is time related. For example, whether the problem can be repeated over a certain period of time and whether there is a significant delay between the successful notification sent time and the actual delivery time.
Related
We use Google Pub/Sub service for being notified when our users receive emails on their Gmail accounts.
We use the Ruby Gmail client (https://googleapis.dev/ruby/google-api-client/latest/Google/Apis/GmailV1/GmailService.html) for watching the Gmail accounts of our user (connected with OAuth authorisation). We expose an endpoint in our Rails app for getting the posted notifications from Google.
It has worked for years without any problem for more than 1000 Gmail accounts. Since two weeks ago, we stopped receiving notifications for some accounts (I would say around 20).
Each account is re-watched once a day (with stop_user() and then watch_user()), so it's not a problem of expired subscription.
Once a notification is not received for an account when there is a new mail, we never receive a notification anymore until it's re-watched. Then, it works for several minutes/hours and then it's broken again. It always happens for the same accounts.
The quotas page on GCP shows that there is not quotas limit exceeded.
I don't know if it's directly related to the Pub/Sub service or if it's a Gmail issue...
Does someone already experienced the same issue ? How can it be investigated / fixed ?
Thank you in advance for your help !
Rémi
As talked in the comments, this seems to be a bug. Adding it as an answer for visibility purposes. You can click on the star next to the issue number to give more priority to the report and to receive updates.
A bug has been created here on the Google issue tracker : https://issuetracker.google.com/issues/208369302
For a few weeks there is an issue with Azure Notification Hub - we have a backend service that registers devices & schedules notifications. When one of the notifications is triggered, then we send it to Azure based on the device type (create the payload and all of that).
The response we get from azure is positive, the notification has been enqueued and is ready to be sent. However, it seems that Azure does not send them all. No error is thrown but only a small percentage is sent. It also does not seem to depend on the device type.
There are no logs to read - or none tha I can find and I cannot pin point the issue.
We have an endpoint that triggers the sending of a notification - we did a test run with 30 notifications (similar and different payloads for the same device) and it all went well.
Not sure how to troubleshoot this or what might cause this. I understood from the documentation that the device might be inactive and then the notification is deleted from the queue after a while. But it seems that the said device receives 1 out of 3 notifications (sent at the same time).
Any feedback would be appreciated.
Edit update:
After upgrading to the Standard plan, we managed to get some more information and it looks like Azure gives back a "Success" with a count of "1" but the device does not receive the notification - the problem is, this happens randomly. It's not always the same device that does or does not receive the notification.
Sorry this isn't a super helpful answer, but could you please open a support ticket in the Azure Portal for us to investigate your particular case? This does not seem like expected behavior so the team will have to look into the logs for your namespace and hub.
One immediate thought - there is de-duplication logic when sending notifications. So within a period of time (something like 15 minutes) if the same notification payload is being sent to the same device, Notification Hubs will automatically drop that duplicate notification.
I have an Azure alerts action group set up which sends an email to myself and 5 colleagues. No problem at all, we all receive the email.
In the same action group I have created another action this time as a Webhook instead of Email/SMS. The webhook URL that I am providing is for a Microsoft Team's channel which has the "Incoming Webhook" connector configured.
When alerts fire and the action group is alerted, the webhook does not appear to be working. Unfortunately, given the restraints of Azure, I cannot actually see any errors or attempts when sending to the webhook.
Anybody else encountered this issue?
Someone else had an issue around this a few weeks ago, perhaps your issue is the same - please check Azure Monitor Alerts using webhook to Microsoft Teams - No messages to Teams
I am using Azure AD Graph API and Microsoft Graph API to communicate the Azure Active Directory . My code parses response received from API and compares error message in some specific error scenarios . Recently I observed one my scenario was failing due to change in response message from the API. I am just curios how these changes are pushed by Microsoft . Are customers notified for these changes ? Are changes released region wise or customer wise ? My code is being used by mates in other geographic reason also , they have not reported any failure till now.
For Example. Previously Error message for expired password was "Forced Password Change" now message is "Password is expired"
Are customers notified for changes ?
Once the service update is applied by Microsoft you will receive a notification if the update was successful or if it was not able to be applied. When any maintenance plan to happen all the partners and user receives notification about that. You could find here
Are changes released region wise or customer wise ?
Usually changes made on regionally. But sometimes data center wise also. But its very rare pointing to specific customer. Some small enhancement take place (Like yours) that's impact less on application and partner as well. In that case you may not receive any notification for that. Other then you would definitely receive mail concerning the issue. For more details you could take look on service life cycle policy
We have been using 2checkout as one of a payment providers for a while now. We run a subscription based service that activate a set amount of time on the users account when we receive a notification.
For some reason in the past few days a number of users (not all) have been receiving notifications of Order Created 3 times, 1 every half an hour.
This is giving then 3 times their purchased time on our system.
Does anyone have any idea why this is happening?
I originally thought it was a case of waiting for the fraud status as on one account, the status was 'wait' for the first 2 notifications. But I have now seen with other users that the fraud check has passed on all 3 notification.
Any help would be appreciated.
Cheers
Nadeem
2Checkout INS notification will attempt to retry for a total of 3 attempts if a successful HTTP response is not returned by your server. You should be able to confirm that they are failing by checking the Failed logs in your 2Checkout account under the Notifications tab. Please contact 2Checkout tech support at techsupport#2checkout.com for assistance with troubleshooting the issue. They will be able to pull the logs to show the response from your server when the notification fails.