Top left New entity button often gives error

Bugs & Issues
1

When creating a new entity using the icon in the top left corner:

image
image588Ă—347 14 KB

Most of the times when I copy past the contents of a regular document, so not even a very long one, then I see:

image
image421Ă—104 3.39 KB

So for me, this popup is useless, I prevent using it because half of the times it rejects saving the content.

Please fix.

2

Can I ask you to provide exact steps to reproduce this issue with sample values you’re trying to submit.

3

I tested with various texts lenghts and types of content.
It has to do with the length, not the content. You can use Lorem Ipsum content to test.

The popup form shows the error at ANY text that is larger than approximately:
Characters: 23700 (approx Tokens: 4,930)

I checked the Console, and asked Copilot to clarify the error I saw.

===

The user has the page “Fibery open and an error message is shown in the DevTools Console for this page. The error message is wrapped within below. Explain the error message and what could have caused it, and provide a way to fix it. 6953.bd0ff4c4.chunk.js:1 POST https://cce.fibery.io/api/forms/json-rpc?m=submit-form;viewId=b033dd67-9b55-4ad0-82e7-b59adc02a2d3;formValues=…;overrideHiddenFields=true 500 (Internal Server Error) 6953.bd0ff4c4.chunk.js:1 POST https://cce.fibery.io/api/forms/json-rpc?m=submit-form;viewId=b033dd67-9b55-4ad0-82e7-b59adc02a2d3;formValues=…;overrideHiddenFields=true 500 (Internal Server Error) Explain the error message from DevTools console

:police_car_light: Error Breakdown:

The message you’re seeing:

POST https://cce.fibery.io/api/forms/json-rpc?... 500 (Internal Server Error)

means that a form submission request to Fibery’s backend failed with a 500 Internal Server Error. This is a server-side error, indicating that something went wrong while the server was trying to process the request.

:magnifying_glass_tilted_left: Possible Causes:

Here’s what might be triggering it:

  • Invalid or malformed formValues: If the data being submitted is missing required fields, has incorrect types, or violates validation rules, the server might crash during processing.
  • Broken automation or script: If the form triggers a Fibery automation or script (e.g. on submit), and that logic throws an error, it can result in a 500.
  • Missing or misconfigured viewId: If the viewId doesn’t correspond to a valid form view, the server may not know how to handle the submission.
  • Backend bug or deployment issue: Sometimes, Fibery’s backend itself might have a bug or be in an unstable state.

:hammer_and_wrench: How to Fix It:

Here are steps you can take to troubleshoot and resolve:

  1. Check the form schema:

    • Ensure all required fields are present and correctly formatted.
    • Validate that formValues match the expected structure.

  2. Inspect automations:

    • If the form triggers any automation, check for errors or misconfigurations in those rules.

  3. Verify the viewId:

    • Confirm that the view ID (b033dd67-9b55-4ad0-82e7-b59adc02a2d3) exists and is accessible.

  4. Use Fibery’s API debugger:

    • If available, use Fibery’s internal tools or logs to inspect the failed request payload and error trace.

  5. Contact support:

    • If the issue persists and you suspect a backend bug, reach out to Fibery’s support team with the full request payload and timestamp.

:light_bulb: Bonus Tip:
If you’re using automation to populate the form or submit it programmatically, try submitting manually with minimal data to isolate whether the issue is with the payload or the server logic.

Want help inspecting the payload or automating a fallback? I’m all ears.

===

I tested with various texts lenghts and types of content.It has to do with the length, not the content.The popup form shows the error at ANY text that is larger than approximately:Characters: 23700 (approx Tokens: 4,930)

===

:magnifying_glass_tilted_left: Thanks for narrowing it down—this is super helpful. Based on your testing, it’s clear that the issue is related to payload size rather than the content type. Here’s what’s happening and how you might work around it:

:police_car_light: Why It’s Failing

When you submit a form with text longer than ~23,700 characters (~4,930 tokens), the server responds with a 500 Internal Server Error. That strongly suggests:

  • Server-side parsing or storage limits: The backend may have a maximum character or token limit configured per field or overall form submission.

  • Database constraints: If the field is mapped to a column with limited capacity (e.g. VARCHAR(16000)), exceeding it can break the insert logic.

  • Timeouts or memory exhaustion: Larger payloads could cause the server to exceed processing time or memory, triggering a 500.

1 Like
4

Thanks, was able to reproduce. Extended a bit an ingestion size for the form data, so couple rich text fields should now be able to pass through.

1 Like