https://community.cloudera.com/t5/Support-Questions/Nifi-Registry-migration-with-nested-process-groups/m-p/319595#M227885 <P>Ok .. Got it resolved. It was needed to remove versioning from the child PGs</P> Wed, 30 Jun 2021 11:31:34 GMT prabhat3422 2021-06-30T11:31:34Z https://community.cloudera.com/t5/Support-Questions/Nifi-Registry-migration-with-nested-process-groups/m-p/319504#M227856 <P>We have a scenario where PG-A has child PGs like PG-A1, PG-A2. Everything works fine with versioning of all PGs along with importing PG-A which imports all child PGs into any other Nifi Development instance.&nbsp;</P><P>However, when we move the registry content from dev to UAT enviroment. Importing of parent PG give error like below. However, child PGs get imported individually without any issue.&nbsp;</P><P>&nbsp;</P><P>"<SPAN>The Flow Registry with ID f9eb8fe6-0176-1000-a53b-838685a98fb8 reports that no Flow exists with Bucket 29a08c71-a056-4e1a-8e8e-0f46abcc50c9, Flow fee2a7e1-3716-42ce-881f-071ef0240fd9, Version 10</SPAN>"</P><P>&nbsp;</P><P>Can you please suggest anything to take of when doing this migration? Any workaround?</P><P>&nbsp;</P><P>Thanks,</P><P>PR</P><P>&nbsp;</P> Tue, 29 Jun 2021 13:11:44 GMT https://community.cloudera.com/t5/Support-Questions/Nifi-Registry-migration-with-nested-process-groups/m-p/319504#M227856 prabhat3422 2021-06-29T13:11:44Z https://community.cloudera.com/t5/Support-Questions/Nifi-Registry-migration-with-nested-process-groups/m-p/319595#M227885 <P>Ok .. Got it resolved. It was needed to remove versioning from the child PGs</P> Wed, 30 Jun 2021 11:31:34 GMT https://community.cloudera.com/t5/Support-Questions/Nifi-Registry-migration-with-nested-process-groups/m-p/319595#M227885 prabhat3422 2021-06-30T11:31:34Z