To provide high performance, data integrity, and predictable behavior, the following limits and constraints apply:
| Limit | Value | Description |
|---|---|---|
| Maximum number of simple + managed schemas per workspace | 10 | You can create up to 10 schemas per workspace, regardless of whether they are simple or versioned. This limit applies universally. |
| Maximum number of singleton schemas per workspace | 200 | This limit is separate from the limit above. |
| Maximum number of records for a managed schema | 10,000 | You can add up to 10,000 records to a managed schema. |
| Maximum number of fields per schema | 100 | - |
| Nesting depth of one-to-many relation | 2-level deep | Only one level of nesting (2 levels deep) is supported. |
| Nesting depth of one-to-one relation | 5-level deep | One-to-one relations can be nested up to 5 levels deep. |
| Size of fetched records for one-to-many relation | 50 | In one-to-many relations, a maximum of 50 records is fetched. |
| Maximum number of one-to-one fields per schema | 5 | - |
| Maximum number of one-to-many fields per schema | 5 | - |
| Maximum number of one-to-many filtered fields per schema | 5 | - |
| Maximum number of Synerise object array fields per schema | 1 per item type | A schema can contain one array field for each item type. The file item type applies to both File and Image fields. |
| Maximum number of items in a Synerise object array field | Depends on item type |
|
| Enabling value uniqueness and searching for a schema field | Only for primitive field types | Only for the following field types, you can enable Enable search & filtering and Unique values only options: string, boolean, number. |
| Maximum number of searchable fields per schema | 10 | Up to 10 top-level primitive fields—fields with basic data types like string, number, or boolean that are defined directly within the main schema and not nested inside objects or arrays—can have the Enable search & filtering option enabled. |
| Maximum unique fields per schema | 5 | A schema can have up to 5 top-level primitive fields—those not nested within objects or arrays and directly defined in the main schema—marked as unique. |
| Maximum number of records in a schema when enabling uniqueness or searching for a field | 5 | You can enable Unique values only or Enable search & filtering for a field only if the schema has 5 records or fewer. |
| Available HTTP methods for creating a connection to an external source | GET and POST |
You can connect to the external sources using only GET or POST methods. |
| Authentication method for external source connections | API key; login and password; SHA256-based authentication | While creating an external source, you can authenticate only with the API key of the external source, login and password, or SHA256 (recommended for authenticating with Eagle Eye) |
| Maximum number of external sources per workspace | 100 | - |
| Maximum duration of a request to an external source | 10 seconds | This limit applies to each request separately. |
| Profile data cache TTL | 60 seconds | After generating an object from a record, profile data is cached. The cache is used for subsequent requests even if the profile was updated |
| File and image cache TTL | 5 minutes | After generating an object from a record, the data of File and Image fields is cached. Previews in the Synerise Portal are not cached. |
| Maximum string length | 32768 | The maximum number of characters for the value of a String or Jinjava code field. This limit applies to default values in the schema and values in records. For Jinjava code fields, this limit does not apply to the generated output. |
| External source response cache TTL | From 60 seconds to 30 minutes, configured per external source | After generating an object from a record, responses from external sources are cached. The cache is used when the external source, headers, query parameters, and request are the same in subsequent requests. |
| Audience validation for referenced (nested) schemas | Top-level schema only | During the generate operation, the audience is validated only for the top-level schema. If the schema contains references to other schemas through relation fields, the audience defined in those referenced (nested) schemas is not validated. |
| Maximum number of response transformers per schema | 20 | Each schema has its own list of response transformers. |
| Maximum number of response transformer versions | 20 | You can access up to 20 previous versions of a transformer. |
| Maximum length of a transformation script | 32 768 characters | - |
| Maximum execution time of a response transformer | 6 seconds | - |
| Maximum personalizations in a schema | 50 | The number of personalizations that you can save in a schema and ten attached to records. |
| Personalization: variants per field | 10 | The number of IF/ELSE IF statements allowed for each field, including the default value. |
| Personalization: references to segmentations | 20 | Each personalization can include references to 20 unique segmentations |
| Segmentations in an object generation request | 50 | Across all the fields and personalizations, an object generation request can result in up to 50 unique segmentation references. |