InspireIT

Power Automate Custom Actions: Exploring the Fundamentals and Diagnosing Issues

Step-by-step | Robotic Process Automation (RPA) with Power Automate

Since its launch, Microsoft introduced “Power Automate” as an important ally for Robotic Process Automation (RPA). However, it still needs some major features to match its major competitor, UiPath.

Microsoft recently unveiled the eagerly awaited Custom Actions within Power Automate, and while they are currently in a testing phase, a few issues have already been identified by users when trying to add the custom actions to the asset library.

How to solve the error: “desktop flow module package is not correctly signed”? and how to overcome the error “custom model cache not found”? Our RPA team has successfully tackled these issues, and throughout this article, we provide a step-by-step guide for each of them.

What are Custom Actions in Power Automate?

Custom Actions are custom modules developed in .NET that can be included in Power Automate flows and used as integrated actions within a library. One small step for man, one giant leap for RPA developers: Power RPA finally supports .NET.

This new feature is like the existing custom activities in UiPath, which allow the creation of functions, methods, or classes in .NET to be imported into the platform and integrated into automations. Furthermore, it enables the reuse of components across different automations.

How to fix the error ‘the desktop flow module package is not correctly signed’?

Error: The desktop flow module package is not correctly signed. 

Fix step: Sign the power shell script file that has the script for creating the cabinet file with the certificate thumbprint.

  • Run the following script in power shell, replacing the following values
  • Replace ‘@CertificateThumbprint’ with the thumbprint from your certificate.
  • Replace ‘@PowerShellScriptFilePath’ with the full path to your power shell script file.


SCRIPT:

				
					$cert=Get-ChildItem -Path:"@CertificateThumbprint"; $cert.EnhanceKeyUsageList;
Set-AuthenticodeSignature -Certificate:$cert
FilePath:"@PowerShellScriptFilePath";
				
			

How to fix the error “custom module cache not found”?

Error: Custom module cache not found

Fix steps:

1 – Go to the following path C:\Users\Username\AppData\Local\Microsoft\Power Automate Desktop\Cache

2- Delete the msalcache.bin3 file, 

3 – sign out from your account, 

4 – close power automate desktop (PAD.Console.Host.exe), 

5 – open Power Automate and sign into your account. 

Warning: The location for your local install of Power Automate Desktop cache may vary. Please make sure to find the correct one and replace the path in the example path. 

Comparisons aside, regardless of the platform you choose, Process Automation (RPA) is crucial for streamlining business processes, getting rid of repetitive tasks, and boosting efficiency while cutting costs. Have you not yet automated your business processes? InspireIT – RPA Makers can help by conducting an audit and guiding your company on the path to digital transformation.

Learn more about the automated process and read our case study.

Stay Updated with the Latest in Intelligent Automation
Don’t miss anything
Subscribe our newsletter

Latest News and Case Studies