--- title: Map Unresolved References slug: blueprint/map-unresolved-references docTags: yO7XZ9PJxDCKZ-Mf4TSYB,HK_rxWrGo8iZHH4PvnxmZ createdAt: 2026-04-17T18:28:53.582Z --- :::CtaButton{label="🟢 Migrator" openInNewTab="false"} ::: This article applies to: 1. Missing xamls being called using *Invoke Workflow* activities in UiPath 2. Missing pages or processes being called by a *page or process reference* stage in Blue Prism 3. Missing taskbots being called using a* Run Task* action in A360 :::hint{type="info"} Ensure you have the correct scope and source RPA tool selected, and that you have generate Rules. See [Using the Rules Table](docId\:aGQEE5DNg_WDm3oCSt_uS) for detailed instructions. ::: # Unresolved References Table Explained | **Column** | **Description** | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Enabled** | By default Rules are disabled. When disabled a Rule will have no affect on export. When enabled, Rule will be applied where applicable. Best practice is to leave a Rule disabled until it is fully configured. | | **Occurrences** | Number of occurrences of this unresolved reference. Click the number to see a list. | | **Scope** | The scope can be either a project or entire Blueprint instance. When using a project as a scope, the rule will apply to all applicable processes within the project. This flexibility allows users to haven different rule sets for different projects. | | **Parameters** | Where to map Inputs and Outputs. When clicked a modal will appear with a table to map which parameters are inputs and which are outputs. | | **ID** | Unique identifier of the missing component. Note this will only be populated for Blue Prism as it is the only tool that includes unique identifier of the component it is attempting to call. | | **Action Name** | The name of the specific activity within the namespace. For Method Invocations this is the method name. | | **Type** | What type of Rule the user wishes to apply: *EXTERNAL\_FLOW, SUB\_FLOW*, *RUN\_ROBINSCRIPT*, *RUN\_VBSCRIPT, RUN\_JAVASCRIPT, RUN\_POWERSHELLSCRIPT, RUN\_PYTHONSCRIPT, RUN\_CSHARPDOTNETSCRIPT, RUN\_VBDOTNETSCRIPT*

**Note **- If *SUB\_FLOW* rules are set to Instance level, all projects must have the target subflow present for the Estimator Dashboard to work. Exports will still work, but the missing subflow will result in a TODO

For more information refer to: [Map to a Script](docId:-aqS_ES0TIzUHibX6x7ux) | | **ID** | When using EXTERNAL\_FLOW, this is the GUID of the Flow in PAD. Blueprint populates in some cases. If you need to manually populate this value, refer to: [Finding PAD Flow Target ID and Name](docId\:tycDmAEDb3_KZHtIFh1Jn)

When using SUB\_FLOW, this will be a unique checksum of the subflow that is populated when you choose the subflow using the picker. Refer to: [Map to a Subflow](docId\:aTRzKxb7fKb7lHmRdRFC6) | | **Name** | When using EXTERNAL\_FLOW, this is the name of the External (Desktop) Flow to map to. Blueprint populates in some cases. If you need to manually populate this value, refer to: [Finding PAD Flow Target ID and Name](docId\:tycDmAEDb3_KZHtIFh1Jn)

When using SUB\_FLOW, this will be the name of the subflow that is generated during export | | **Script** | When using any of RUN\_\SCRIPT you will enter your script here. Refer to: [Map to a Script](docId:-aqS_ES0TIzUHibX6x7ux) | *** # UiPath For UiPath unresolved references are instances of Invoke Workflow actions where the named workflow is missing within Blueprint. There are two typical cases where this occurs: 1. The workflow was missing from the imported data. In this case the easiest remedy is to re-export from UiPath ensure the workflow is included in the export, then re-importing to Blueprint. Once you do this, the rules should no longer be generated. 2. Another case is when the reference is being made using a variable. In this case the reference is resolved at runtime and it is impossible to know during code-conversion. When this occurs you need to identify the components will be called at runtime either by analyzing the source UiPath code or running it and observing. Once you have identified the needed components, you then need to ensure they are included into the generated PAD flow. You can do this using the "Add Subflows" option when exporting as shown in the picture below. ::Image[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/7Zaj7tN9b79KE3DQUBV92-20260605-221311.png" size="70" width="1045" height="801" darkWidth="1045" darkHeight="801" position="center" showCaption="false"} If the missing component exists in Blueprint but the references to them are simply broken, then you can configure a rule to resolve the issue. Choose Target Type = SUB\_FLOW then click the pencil in the ID column and choose the component. Ensure the rule is enabled before exporting. For more information, see [Map to a Subflow](docId\:aTRzKxb7fKb7lHmRdRFC6) If the missing components simply cannot be found, you can instead substitute a script for each of the references, or substitute a call to an external flow. See [Map to a Script](docId:-aqS_ES0TIzUHibX6x7ux) or [Map to an External Flow](docId\:Nu3bqTvWhkapcB7YG_ML7) for more information. *** # Blue Prism For Blue Prism unresolved references are instances of page-reference or process-reference stages calling pages or processes that do not exist. You should first attempt to determine why these objects were missing from the .bprelease file, then produce and import a new .bprelease file that has them. If they are simply unavailable then you can configure the unresolved reference rule to have these references refer to one of an external flow (refer to [Map to an External Flow](docId\:Nu3bqTvWhkapcB7YG_ML7)), a subflow (refer to [Map to a Subflow](docId\:aTRzKxb7fKb7lHmRdRFC6)), or use an embedded script (refer to [Map to a Script](docId:-aqS_ES0TIzUHibX6x7ux)). *** # A360 For A30 unresolved references are instances of Run Task actions that refer to a taskbot that does not exist in the imported A360 data. You should first attempt to determine why these objects were missing from the .zip file, then produce and import a new .zip file that has them. If they are simply unavailable then you can configure the unresolved reference rule to have these references refer to one of an external flow (refer to [Map to an External Flow](docId\:Nu3bqTvWhkapcB7YG_ML7)), a subflow (refer to [Map to a Subflow](docId\:aTRzKxb7fKb7lHmRdRFC6)), or use an embedded script (refer to [Map to a Script](docId:-aqS_ES0TIzUHibX6x7ux)).