Is anyone currently encountering any issues with the Workflow action pack? Any workflow we have action pack functions in is failing / suspending. We've made no changes to any of our workflows for some time now, so the issues have come as a surprise.
Hi @Jaydius,
Please retry the flow and let me know if the issue persists. If yes, share a screenshot with the error message.
Best regards,
Petr
Plumsail team
One particular workflow is using the send email with attachment and presenting this error:
Exception: The request failed. The remote server returned an error: (401) Unauthorized.
We’ve checked credentials are correct. There has been no changes to these recently and the workflow had been working fine for over 18 months.
Another workflow using the 'Get items by query' function is throwing the following error:
RequestorId: aa59fede-6d84-e561-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130575155, Microsoft.SharePoint.SPFieldValueException","message":{"lang":"en-US","value":"Cannot complete this action.\u000a\u000aPlease try again."}}} {"Transfer-Encoding":["chunked"],"Vary":["Origin"],"X-SharePointHealthScore":["3"],"X-SP-SERVERSTATE":["ReadOnly=0"],"DATASERVICEVERSION":["3.0"],"SPClientServiceRequestDuration":["79"],"X-DataBoundary":["None"],"X-1DSCollectorUrl":["https://mobile.events.data.microsoft.com/OneCollector/1.0/"],"X-AriaCollectorURL":["https://browser.pipe.aria.microsoft.com/Collector/3.0/"],"SPRequestGuid":["aa59fede-6d84-e561-9cfe-1385ddb482aa"],"request-id":["aa59fede-6d84-e561-9cfe-1385ddb482aa"],"MS-CV":["3v5ZqoRtYeWc/hOF3bSCqg.0"],"Strict-Transport-Security":["max-age=31536000"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"Content-Security-Policy":["frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com *.microsoft.com securebroker.sharepointonline.com;"],"MicrosoftSharePointTeamServices":["16.0.0.23005"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Tue, 18 Oct 2022 21:32:52 GMT"],"P3P":["CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI""],"Server":["Microsoft-IIS/10.0"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Exception from activity Throw If Sequence Sequence TryCatch Sequence Microsoft.SharePoint.WorkflowServices.Activities.RetryForDurationPolicy HttpPost UpdateListItem Microsoft.SharePoint.WorkflowServices.Activities.UpdateListItem Then If Then If Update Record Sequence Flowchart Sequence Update Qualification Record.WorkflowXaml_999c034c_4ba8_4ae0_b631_3640cbae2f9a
Hello @Jaydius,
We also haven't upgraded the product recently.
Could you clarify is it Online or On premises version?
Best regards,
Petr
Plumsail team
We have the Online (Office 365) version.
As these issues have only started recently, could they be in relation to Microsoft disabling Basic Authentication? I see Nintex Workflows have recently updated with the following note:
The Username and Password fields in the configuration of Exchange Online actions have been replaced with the Authorizing user field due to Microsoft deprecating basic authentication.
Hi @Jaydius,
Do you use Send Email with Attachments (Exchange) action?
If yes, could you try Send Email with Attachments action (not Exchange) and specify correct smtp server settings?
Best regards,
Petr
Plumsail team
1 Like
It appear the exchange action was the issue. Changing to the SMTP action fixed the authentication error. Thank you for your help Petr!
1 Like