{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":23028,"path":"intelligent-experiences/config-inbound-payload-size.md","title":"Increase maximum inbound content length for scripted REST APIs","bundle":null,"doc_type":null,"release":"australia","body":"\n# Increase maximum inbound content length for scripted REST APIs\n\nIncrease the maximum allowed inbound content length for scripted REST APIs when automated agentic evaluation runs fail due to inbound payload size limitations.\n\n## Before you begin\n\nRole required: admin\n\n## About this task\n\nIf evaluation runs fail due to inbound payload size limitations, you can increase the maximum allowed inbound content length for scripted REST APIs by modifying the system property **glide.rest.scripted.max\\_inbound\\_content\\_length\\_mb**. The default value is 10 MB. You can set this to 12 MB for moderately larger payloads or 25 MB for significantly larger payloads, or adjust to other values as required by your environment and governance policies.\n\n**Note:** Increasing the inbound content limit may impact memory consumption and request processing. Review platform capacity and governance guidelines before setting higher values.\n\n## Procedure\n\n1.  Navigate to **System Definition** &gt; **System Properties**.\n\n2.  Search for the property **glide.rest.scripted.max\\_inbound\\_content\\_length\\_mb**.\n\n3.  Update the value from the default **10** to one of the following:\n\n    -   **12** MB for moderately larger payloads\n    -   **25** MB for significantly larger payloads\n4.  Save the changes.\n\n5.  Re-run the evaluation.\n\n\n"}}