---
title: 9. Known Limitations
slug: docs/9-known-limitations
docTags: 
createdAt: 2026-06-08T08:22:19.576Z
---

Operational constraints and edge cases to be aware of when using Profile Updater in customer-facing demo environments.

## Postman cURL paste truncation

Postman silently truncates large pasted cURL commands. If the JSON body exceeds \~10 KB, the paste is cut off mid-payload — the paste appears to succeed but results in a malformed request with no visible error.

✅ **Workaround:** Save the JSON body from the payload viewer to a local file and use --data @payload.json in your cURL command, or submit the update directly via the **Update profile** button.

## Profile update propagation delay

After clicking **Update profile**, changes typically propagate to the AEP Real-time Profile store within a few seconds, but during high-ingestion periods this may take longer.

✅ **Workaround:** Use **Refresh profile** after a brief wait to verify the update has been applied.

## DSN prerequisite dependency

The tool requires both a DSN Streaming Inlet and DSN schemas/datasets to be provisioned in the target sandbox. If either readiness check fails, the search and edit functionality is unavailable until the sandbox is configured correctly.

## Session state is ephemeral

Pending form changes are held in browser memory only. If you navigate away or refresh the page before clicking **Update profile**, all uncommitted edits will be lost.

✅ **Workaround:** Use **View payload** to save a copy of your pending changes before navigating away.

## Identity and system fields are read-only

Fields declared as identity descriptors or managed by the AEP system cannot be modified through Profile Updater. Attempting to modify them via direct API calls outside the tool may result in merge conflicts or orphaned identity nodes in the identity graph.