# Infinite Reload Loop in Visual Editor for Programmatically Created Content

**URL:** <https://forum.builder.io/t/infinite-reload-loop-in-visual-editor-for-programmatically-created-content/15942>\
**Category:** Bugs\
**Created:** [November 12, 2025, 2:47pm UTC](https://forum.builder.io/t/infinite-reload-loop-in-visual-editor-for-programmatically-created-content/15942 "2025-11-12T14:47:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicolle](https://avatars.discourse-cdn.com/v4/letter/n/8c91f0/32.png) [@nicolle](https://forum.builder.io/u/nicolle)\
**Post date:** [November 12, 2025, 2:47pm UTC](https://forum.builder.io/t/infinite-reload-loop-in-visual-editor-for-programmatically-created-content/15942/1 "2025-11-12T14:47:42Z")

</div>

I have a drag and drop Blog Post and I’m experiencing an infinite reload loop in the [Builder.io](http://Builder.io) visual editor when trying to edit content entries that were programmatically created via the [Builder.io](http://Builder.io) Write API. The editor continuously alternates between the edit URL and non-edit URL without successfully loading the preview iframe.

I also cannot archive these entries.

**Specific behavior:**

- URL alternates between:

- The visual editor never stabilizes and keeps reloading

- Content works perfectly when rendered locally OR Preview URL

- Content created manually through the [Builder.io](http://Builder.io) UI works fine in the editor

**Link to affected content:**

- Example entry: `https://builder.io/content/4c6dae2e5db7422ea856eaa0d724d146/edit`

- Model: `resource-guide-model`

**Code stack you are integrating Builder with**  
_NextJS_

---

<div class="post-metadata">

**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\
**Post date:** [November 13, 2025, 11:26am UTC](https://forum.builder.io/t/infinite-reload-loop-in-visual-editor-for-programmatically-created-content/15942/2 "2025-11-13T11:26:27Z")

</div>

Hello @nicolle,

We’ve investigated the issue, and it appears that it may be related to the `data.blocks` field being sent in your Write API request body.

Here’s the Content API call for the [affected entry](https://builder.io/content/4c6dae2e5db7422ea856eaa0d724d146/edit) for your reference:  
[https://cdn.builder.io/api/v3/content/resource-guide-model?apiKey=9ddb1921a754418bb8cdf6ce5211998e&query.id=4c6dae2e5db7422ea856eaa0d724d146&limit=1](https://cdn.builder.io/api/v3/content/resource-guide-model?apiKey=9ddb1921a754418bb8cdf6ce5211998e&query.id=4c6dae2e5db7422ea856eaa0d724d146&limit=1)

Could you please try sending the request **without the** `data.blocks` **field** in the request body and let us know if that resolves the issue?

Additionally, if you can share the **JSON payload** you are currently sending, we can review it in more detail to help identify the root cause.

Looking forward to your update.

Thanks,