I have created a Skypebot application in Node JS. Recently we face slowness for chat messages in Skypebot . Some times we don't see messages in skype , once we close open the skype messages are displayed at once.
Skype bot app uses some commands to communicate to other users, but due to the slowness of message it doesn't executes the commands properly.
These issues happened recently only and we are facing this for last 4-5 months.
Any suggestion/help, how I could resolve this?
Skype bots are deprecated. I recommend switching to another platform, like Teams.
Related
I have 2 tenants and in one of them Teams can send/receive messages just fine, in another tenant, i can search for external contacts (Skype) but I cannot send or receive messages it always gives me this error message:
"We ran into a problem sending your message. Please share diagnostic code 504/1008 with your admin to help them troubleshoot the issue."
Troubleshoot I did:
The configurations in Teams admin center are exactly the same in both tenants
I cannot confirm (I´m a global reader but some settings I cannot see) but it´s possible that we have some differences in Azure, although I don´t think this impacts Teams
Checked the logs and the only thing related i could find was this:
SfBInteropServiceGateway: Interop message: 1675175961408 failed with unknown errorcode. {"messageId":"1675175961408","Thread.Id":"19:prhjiknlw6vvfq5v35jveri5au3icj3utj3udd2ks5ejapmefvjq#sfc.unq.gbl.spaces","errorCode":"504/1008","status":"RecipientPresence: isUnifiedPresence=undefined, status=Unknown, availability=Offline","type":"unknown"}
The options Set-CsExternalAccessPolicy -EnablePublicCloudAccess and Set-CsTenantFederationConfiguration-AllowPublicUsers are also exactly the same in both tenants
search on the web didn´t do much
Any suggestion?
Thanks in advance!
As requested here i am reposting this question.
I have the same issue as PitcherIT mentions here
I am trying to configure Connectors for my Team and when I click on the Connectors
option, the sub pane starts to load and then errors with;
:-(
Something went wrong.
Something went wrong
RequestId: unknown
Server: unknown
Date: null
As the original thread is closed i am adding my experience in a new question.
I can add new connectors to the channel going via Apps>Connectors>Incoming Webhook
But i cannot view already configured connectors or change them due to the error message.
What i noticed is that the new webhooks have the format
https://xtpgroup.webhook.office.com/webhookb2/
while the old one starts with
https://outlook.office.com/webhook/
Maybe that is connected with the strange error message when viewing the connectors.
How can i change the configured connectors without deleting and recreating the whole channel?
Edit: Screenshot of the Error message
We have raised a bug internally. We will let you know about updates.
Thanks.
I had a similar issue where I wasn't able to view Configured Connectors for a Channel in the Teams app. There wasn't an error message, but the loading icon never resolved. The workaround for me was to use the Teams web app and configure Connectors there.
Please tell me how you can send a message to a bot without a command, and then it will process it? So that after restarting but it continued to process? I started developing bots quite recently, but I still don't understand a lot of things. So far, I only came up with the idea that you can record the ID of the created message, then check it...
thank you in advance!
Azure notification hubs have a feature that allow for subscribing to various topics in a many to many relationship. (many devices to many declared topic strings)
Suppose I take these steps:
I send an iOS device a notification, "test 1".
The device goes offline.
I send "test 2"
I send "test 3".
The device comes back online.
APNS only sends "test 3". Test 2 was dropped
Not to mention that APNS will only notify the most recent event "Test 3", it can also drop additional alerts in iOS 11 if I exceed the 30 maximum per day.
One of the things I like about Azure Hub service, is that I can manage that subscription "state" in an external storage. Now however, it seems I have to track the subscriptions myself, rebuilding part of the Azure HUB architecture... archiving out the subscriptions, topics, etc so the device can query the server for all missing events.
Question
How do I reconcile the features of Azure Hub and topic subscription with the issue of dropped APNS pushes?
You're correct that there's nothing ANH (or you as a developer) could do about the dropped notifications because that's the way ANPS is designed. Which means that the solution to your problem would really depend on what kind of application you're building, the architecture and user scenarios you're targeting.
A couple of ideas I have in mind which may or may not works for you depending on what you're trying to do are:
Send a silent push to the topic once in a while that would trigger the app to query the server on whether something has been missed
If the nature of the app is such that people open it often anyway, then you could do a background check at the time they open the app
Of course, in both of these scenarios, you'll have to build some additional infrastructure on your end to keep track of which device received or missed certain notifications. One thing that might help you not to have to rebuild parts of the NH that are already there is using Pet Message Telemetry (PMT). I haven't experimented with dropped notifications, but hopefully, there's a way to tell a dropped vs delivered message apart using PMT (looks like Dropped value of the PnsErrorDetailsUri field is something similar to what you need). And having that might help you simplify and reduce the amount of data you need to keep on your end to be able to tell whether someone had missed a notification or not.
We have recently started using hornetq on a project and we use durable subscriptions to topics. However we have no control over the subscribers. What we would like to do is timeout the durable subscriptions if the client hasn't connected in the last 24 hours. There are a couple reasons for wanting to do this. The main reason is that the client id could change or the connecting client might just disappear.
Does anyone have any ideas?
Thanks in advance.
That seems a nice feature to have. You should open a feature request.
Meanwhile you could use management API to discover the queues you have, and the number of consumers on them. At this point you would have to control such thing outside of hornetq.
We would accept contributions if someone implemented the feature, and we could collaborate on the process.