Environment
---------------------
Transfer CFT 2.3.0
Gateway 6.11.4
PESIT Protocol

Problem
------------------
* Transfer initiated from CFT, using PESIT protocol
* Error on CFT side :
remote creation reject 613 ACR 204
* Errors on Gateway side :
"a transfer is already started", "file already exists"

Explanation :

-- The transfer in error has the same transfer id as an already existing transfer in Gateway (xfer ident)
-- For PESIT the transfer ident is set by the sender, CFT in this case
-- Transfer id must be unique for each transfer with a partner with the same application
-- When CFT is sender, it may happen that the same xfer id is used each month, considering the way CFT constructs the id

Solution :  

-- Gateway receives some files from CFT using PeSIT : mailbox should be purge by keeping a 30 days history (keep_last_day parameter set to 30 in the purge option with a purge done every day) to prevent the error "a transfer is already started" to occur.

-- If you need a larger number of days in the mailbox use the Statistics (Gateway help > Managing transfers > Monitoring transfers > Command line operations > Managing Statistics files).