Microsoft recently announced that it will be ending support this year for the workflows component of SharePoint 2010 Online, as well as depreciating that component for SharePoint 2013 Online.

If you read the blog above specifically the comments, you will get a sense as to why this is a big deal.

End of support means no new patches will arrive from Microsoft, including security patches. The intention from Microsoft is to get organisations to move to using Power Automate (formerly known as Microsoft Flow) instead of SharePoint Workflows. The deadline announced by Microsoft only applies to organisations using SharePoint Online services, hosted by Microsoft.

The deadlines announced from Microsoft are as follows:

• Starting August 1st, 2020, SharePoint 2010 workflows will be turned off for newly created tenants.  
• Starting November 1st, 2020, Microsoft will begin to remove the ability to run or create SharePoint 2010 workflows from existing tenants.

For customers using SharePoint 2013 Workflows, the component will continue to work with SharePoint 2013 Online, however Microsoft is still depreciating the component. In a nutshell, this means that Microsoft isn’t planning to do further software development work on workflows, although security patches will continue to arrive.

Microsoft is planning to turn off workflows for new SharePoint 2013 Online, starting in November 2020. Your organisation will still be able to use it, you will however need a certain PowerShell script to activate workflows.

If you have an A Team agreement with us we would have already resolved these issues for you.

John Lui has also created the "Ninja List: The great migration of SharePoint Workflow to Power Automate" which provides plenty detail on how to upgrade those essential 2010 Workflows

I was upgrading a SharePoint 2010 farm using PSConfig.exe as shown below

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

After the timer stopped at “The farm is being upgraded in the timer service process. The task is 10.00% completed.” it failed and after searching the LOGS I found the below error.

Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it. Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=,DC=,DC=com doesn't exist in the directory. at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

To resolve the the issue I used this walkthrough.

http://blogs.msdn.com/b/opal/archive/2010/04/18/track-sharepoint-2010-installations-by-service-connection-point-ad-marker.aspx