OK we will try to identify an external resource.
Hi @Marian_Koreniuk , we are checking the errors one by one by looking at where in the method the error occurs and what external resources are called just before the error happens.
Based on this analysis, we think there is a possibility it may be Close.com and are creating a ticket for them to investigate.
However, there is one method which leads us to think it may be Backendless.
This is a front-end method
As you see above, it contains VERY simple logic. It basically toggles a component’s visiblilty. And it creates an error sometimes, but not always.
Hello @Andreas_Marinopoulos!
Could you please let us know if you’ve received any information from Close.com that might help us resolve this issue?
Regards,
Alexander
We have confirmed it is not Close.com. We are also checking where it is Slack, as Slack is also present in all our methods. I will revert soon.
Hello @Alexander_Pavelko
Question:
- How do I connect to the network that our system from backendless uses to run the connection test from Slack ?
- This is to confirm if the connection error 111 is from the slack sides or not
Thank you