> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/issues.md). # Known errors ## Anomalous growth in database size In versions **3.2.7 and earlier**, an anomalous growth in the database size has been detected. This increase was caused by the table *pending\_files\_audit*, which stored audit records. These records grew continuously and caused: * Progressive increase in database size * Higher disk space consumption * Possible performance degradation in the long term To correct this behavior, a cleanup process has been implemented that completely removes the records from this table, since they are not necessary and do not provide functional value: * *truncate\_pending\_files\_audit.bat* is the script responsible for performing this cleanup in Windows * *truncate\_pending\_files\_audit.sh* is its equivalent for Linux systems In versions **3.1.6 and later within the 3.1 branch**, the issue has been fixed: * The table has been removed *pending\_files\_audit* * Its associated auditing mechanism has been removed ### Instructions for running the cleanup script 1. Copy the script to the path where the database maintenance scripts are located: directory `bin\psql` within the Editran Connect installation path 2. In the case of Linux, grant execution permissions to the script by running the command `sudo chmod +x truncate_pending_files_audit.sh` and change the owner to *editran* by running `sudo chown editran:editran truncate_pending_files_audit.sh` 3. Run the script corresponding to the operating system 4. Repeat this process periodically to prevent the database size from growing anomalously again ## Editran protocol version not reported In versions **3.2.7 and earlier**, it was detected that the license information did not include the **Editran protocol version**, showing only the Editran version according to the license. This could cause confusion when identifying the actual Editran protocol version in use, since that version does not necessarily match the Editran product version. This behavior has been corrected in versions **3.2.8 and later**, where the corresponding information has been added on the screen *Local configuration → License* for the Editran protocol version. In versions **3.1**, it was detected that the license information did not include the **Editran protocol version**, showing only the Editran version according to the license. This could cause confusion when identifying the actual Editran protocol version in use, since that version does not necessarily match the Editran product version. This behavior has been corrected in versions **3.2.8 and later**, where the corresponding information has been added on the screen *Local configuration > License* for the Editran protocol version. ![license\_data](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-8153034833ae547807ce85c0403874601ea2d8d3%2Fdatos_licencia.png?alt=media) ## Incorrect scheduler execution with 60-minute tasks and time slots In versions **3.1**, it has been detected that the task scheduler did not run correctly when tasks were configured with a periodicity of 60 minutes or more and, in addition, execution time slots were defined. This behavior was due to an error in the logic for calculating execution times, which caused the scheduler not to schedule tasks correctly, preventing their execution at the established times. This issue has been fixed in versions **3.2.8 and later**, where the logic for calculating the scheduler's execution times has been reviewed and corrected when tasks have time slots, regardless of the configured periodicity. ## Behavior detected in the certificate store (keystore) when importing file groups In versions **3.2** it has been detected that, when importing a group of files through the option *Import > Import file group*, an inconsistency occurred in the certificate store (keystore) when the file group could not be imported correctly, either due to an error in the file group format or any other cause that prevented its import. Although the import process was interrupted and not completed, the system added the certificates associated with the file group that was being attempted to be imported to the certificate store (keystore), which caused an inconsistency between the state of the certificate store and the actual system configuration. This issue has been fixed in versions **3.3**, where the import process for file groups has been reviewed and corrected to ensure that certificates are only added to the certificate store (keystore) if the import process completes successfully. In version 3.2, an undesired behavior was identified during the import of file groups using the option Import → Import file group. When the group could not be imported correctly—whether due to an incorrect format, a corrupted file, or any other error—the system stopped the process, but still partially added the certificates associated with that group to the keystore. This behavior caused a mismatch between the actual state of the certificate store (keystore) and the system's effective configuration, generating an inconsistency that could affect subsequent operations. This error has been corrected in version 3.3. From this version onward, the system only adds certificates to the keystore if the group import completes successfully, thus ensuring full consistency between the certificate repository and the system configuration. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.