> 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-v2.1-en/issues.md).

# Known issues

## Error when performing operations on channels migrated from TELEGC

The old TELEGC sessions were created with the tuple cod.remote-TELEGC instead of the cod.local-remote-TELEGC format. This causes an error when attempting to perform any operation in Connect on these channels. To solve this problem, once the entire migration process has finished, the script must be executed *GCFIX.bat* / *GCFIX.sh*

### Instructions for running the correction script

1. Extract the program to the Editran Core installation path
2. Grant permissions to the necessary files. In Linux, the user is editran.
3. Run script

## Abnormal growth in database size

In versions **2.1.18 and earlier**, an abnormal growth in 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 usage
* Possible long-term performance degradation

To correct this behavior, a cleanup process has been implemented that completely deletes the records from this table, since they are neither necessary nor 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 **2.1.19 and later**, the problem has been solved:

* 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. For Linux, grant execute 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 abnormally again

## Incorrect execution of the scheduler with 60-minute tasks and time slots

In versions **2.1.18 and earlier**, it has been detected that the task scheduler was not running 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 the tasks correctly, preventing them from running at the established times.

This problem has been fixed in versions **2.1.19 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.


---

# 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-v2.1-en/issues.md?ask=<question>&goal=<endgoal>
```

`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.