Merge pull request #4907 from MicrosoftDocs/jdaly-master-fix-2527

Jdaly master fix 2527

Author: JimDaly

powerapps-docs/developer/data-platform/catalog-catalogassignment.md

@@ -2,7 +2,7 @@
 title: "Catalog and CatalogAssignment tables (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to use the Catalog and CatalogAssignment tables to expose events in your solution"
 ms.custom: ""
-ms.date: 07/06/2021
+ms.date: 07/12/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -251,13 +251,13 @@ GET [Organization URI]/api/data/v9.2/customapis?$select=customapiid&$filter=uniq
 This is most easily done using the Web API. The following example will return the `workflowid` of a custom process action with the `uniquename` of `ExampleCustomProcessAction`.
 
 ```http
-GET [Organization URI]/api/data/v9.2/workflows?$select=workflowid,uniquename&$filter=category eq 3 and type eq 2 and endswith(uniquename,'ExampleCustomProcessAction')
+GET [Organization URI]/api/data/v9.2/workflows?$select=workflowid,uniquename&$filter=category eq 3 and type eq 1 and endswith(uniquename,'ExampleCustomProcessAction')
 ```
 
 > [!NOTE]
 > The `uniquename` of the workflow doesn't include the customization prefix that is prepended to the name of the custom process action in the Web API. If the action you call from the Web API is named `new_ExampleCustomProcessAction`, the workflow uniquename will be `ExampleCustomProcessAction`.
 >
-> Make sure you to access the row where [Type](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Type) is `2`. This is the activated workflow.
+> Make sure you to access the row where [Type](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Type) is `1`. This is the workflow definition.
 >
 > Custom process action workflows have the [Category](/powerapps/developer/data-platform/reference/entities/workflow#BKMK_Category) value of `3`.
 

powerapps-docs/developer/data-platform/troubleshoot-plug-in.md

@@ -2,7 +2,7 @@
 title: "Troubleshoot plug-ins (Microsoft Dataverse for Apps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn what plug-in errors can occur and how to fix them." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 03/16/2021
+ms.date: 07/12/2021
 ms.reviewer: "pehecke"
 ms.service: "powerapps"
 ms.topic: "article"
@@ -24,7 +24,7 @@ This topic contains information about errors that can occur due to plug-in execu
 ## Error: No Sandbox Worker processes are currently available
 
 Error Code: `-2147204723`<br />
-Error Message: `The plug-in execution failed because no Sandbox Worker processes are currently available. Please try again.`
+Error Message: `The plug-in execution failed because no Sandbox Hosts are currently available.`
 
 This error simply means that the worker process running your plug-in code crashed. The reason it crashed may be your plug-in, but it could also be another plug-in running concurrently for your organization. Because the process crashed, we can’t extract any more specific information about why it crashed. But after examining data from the crash dumps after the fact, we have found that this usually happens for one of the 4 reasons below: