RPA Import Log

every import into migrator automatically generates an rpa import log file containing a record of all processes and sub processes imported if all processes imported successfully, you will not need to reference this file if any process failed to import, the log file name will display an asterisk ( ) open the file to review failures — failed processes appear at the top along with the reason for the failure failures are typically caused by unsupported structures such as infinite loops blue prism additional log entries blue prism imports may generate additional log entries for the following conditions orphaned stages blue prism processes can contain orphaned stages — stages disconnected from the process flow that will not execute at runtime if orphaned stages are detected, the log file name will display an asterisk search the log for "warning orphaned stages" to find the affected processes or objects, listed by their blue prism stage names initialize stages stages in the initialize tab of a blue prism object execute once before any other actions blueprint does not convert these stages if initialize stages are present, the log file name will display an asterisk and the following message will appear in the log "info the initialize page for this object contains stages, and this will not be exported to pad as part of any call tree that uses this object's actions please review the logic in the initialize page and manually incorporate as needed into any converted flow that uses this object please consider redesigning source rpa if necessary " duplicate stage ids in rare cases where a blue prism process was edited directly in a text editor, the resulting file may contain duplicate stage ids blueprint handles these the same way blue prism does — only the first occurrence is kept if duplicate stage ids are detected, the following warning will appear at the top of the log "info duplicate stage ids found across pages processid/objectid \<process object id>, stage id \<stageid>"