Known system limitations

ХТRF platform, like any other software, has some technical limitations concerning the database size, maximum number of characters, etc. Our QA team regularly tests the system capabilities using the available data and known scenarios on the databases we have access to. However, we can't guarantee that our team can test and confirm all possible scenarios and configurations for a particularly large number of entities.

If you intend to work with large amounts of data, especially if you already have data amount-related problems with other software, please reach out to your main point of contact before proceeding.

It is always better to start on a smaller scale and follow up when the performance is satisfactory.

In particular, please be aware of the following restrictions:

1	There is a hard limit on uploaded file size - 1GB. Please be aware that some file types, especially compressed files, may have much lower size limits due to complex processing and analysis, most commonly related to CAT tool integrations. It is not possible to estimate this limit beforehand. Excessive processing of such files may degrade system performance and lead to a crash.
2	There is a limit to importing entities from previous systems - 10,000 entities of each kind, for example, 10,000 previous customers. Please take extreme caution to only import necessary and legally allowed personal data into the system.
3	There is a soft limit to the number of concurrently logged-in users (between 50 and 100), which is heavily dependent on usage patterns and server performance. Scaling above 100 concurrent users will likely require the multinode setup with horizontal user distribution. Exceeding a certain user amount will degrade application performance.
4	Text fields are limited to 20,000 characters.
5	Some text fields in the system allow you to use formatting and paste text from other sources. The contents of those fields should be limited to 10,000 characters (bytes).
6	The total content of a CRM e-mail, including its Subject, Recipients, and Message fields, must not exceed 25,000 characters.
7	The soft limit of contact persons per single company entry is 100. While the system allows for more, it may degrade system responsiveness.
8	The size of a single translation project is limited. Smart projects should have no more than 200 tasks per project and 100 jobs per task. For integrated Smart projects, we recommend having no more than 100 language combinations. System performance in integrated projects is heavily dependent on the complexity and scale of the project. The number of steps, jobs, and files, as well as file size, can impact system responsiveness. We strongly advise keeping integrated projects within a manageable scope to ensure optimal performance. Classic projects should have no more than 50 tasks, 50 activities, 50 language combinations, and an overall storage size of 10GB.
9	While the system allows you to add custom data fields to certain entities, their amount is limited to 10 for each type. You should not store large amounts of data in the custom fields, as this impacts performance significantly.
10	XTRF also allows you to add scripted virtual columns, similar to custom fields, but dynamically calculated during view rendering. Using too many or too complex virtual columns will increase the application's CPU usage and reduce its performance.
11	XTRF macros can process up to 500 entities.
12	When using CAT tool integrations, the XTRF responsiveness heavily depends on the third-party system responsiveness. Make sure to reduce the network latency between systems and ensure sufficient capacity for the external system.
13	In load-heavy Smart Projects (e.g., those where a CAT tool integration, job splitting, and process with more than six steps are enabled simultaneously), we recommend limiting the number of target languages to around 50 for better responsiveness.
14	While API responses, especially browse, allow for a large number of results at one request, it is better to use pagination and scroll through multiple smaller result sets. Large result sets will be slow to calculate, especially with virtual columns.
15	The vendor portal has shown poor performance when a vendor has over 100 invoices.
16	Project Confirmations can only be sent with no more than 5 attachments.
17	Very large invoices (containing over 3000 tasks) cannot be deleted properly.