# Pega 24.2 Blueprint Import Failure – "Create new record failed: Branch ruleset not created"

**URL:** <https://forums.pega.com/t/pega-24-2-blueprint-import-failure-create-new-record-failed-branch-ruleset-not-created/13738>\
**Category:** User Experience\
**Created:** [October 12, 2026, 8:30am UTC](https://forums.pega.com/t/pega-24-2-blueprint-import-failure-create-new-record-failed-branch-ruleset-not-created/13738 "2026-10-12T08:30:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ShubhamJ](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@ShubhamJ](https://forums.pega.com/u/ShubhamJ)\
**Post date:** [October 12, 2026, 8:30am UTC](https://forums.pega.com/t/pega-24-2-blueprint-import-failure-create-new-record-failed-branch-ruleset-not-created/13738/1 "2026-10-12T08:30:23Z")

</div>

We are currently creating a new application using **Blueprint** in **Pega 24.2**. Our existing application is built on the **UI Kit** architecture, while the new application is being created using **Constellation**.

During the Blueprint import process, we are encountering the following error:

> **“Create new record failed: Branch ruleset not created”**

**Background:**

- Existing application: UI Kit based
- Pega version: 24.2
- New application: Generated through Blueprint and based on Constellation architecture
- Issue occurs during Blueprint import/application creation

Could you please help us understand:

1. What could be causing the branch ruleset creation failure during Blueprint import?
2. Are there any prerequisites, permissions, or ruleset configurations that need to be verified before importing a Blueprint-generated application?
3. Is there any known limitation or compatibility consideration when creating a Constellation application in an environment that already contains UI Kit-based applications?
4. Are there any logs, diagnostic steps, or reference documents that can help us troubleshoot this issue?