RequestorId: 410ad286-4516-9755-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult) at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at Microsoft.Activities.Messaging.SendHttpRequest.OnReceiveResponse(NativeActivityContext context, Bookmark bookmark, Object value) at System.Activities.Runtime.BookmarkWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager) Exception from activity SendHttpRequest Send Task Call web service async Plumsail.ActionsPack.CallServiceAsync SmtpSendEmail Plumsail.ActionsPack.SmtpSendEmail Then If Firmante2 Sequence Flowchart Sequence WF_Solicitud_De_Viaticos.WorkflowXaml_92772550_5a79_473f_a8ad_3225e020ae7f
The current issue is that Microsoft has blocked our main account due to a phishing report on one of our public web forms. The phishing issue was known, and we were taking measures to combat it, but it seems that Microsoft has taken matters into its own hands.
Unfortunately, all of our services were deeply integrated with the main account, and we didn't expect it to be completely blocked with no warning. We're currently transferring services to our reserve accounts (this will take time), and we're also contacting Microsoft's support to resolve the matter with the main account. As soon as there is any progress - we'll let you know!