Implementation:

In Pega 8.7.4 version, we have integrated AWS provided S3 bucket with credentials using the repository rule for uploading input files and configured a file listener for processing the files uploaded in it. Then the processed files will be sent in an email to external team.

Issue:

When a file listener is newly created (or) deployed in higher environment for the first time,  it will works as expected (i.e) once file got processed, an email will be sent and the processed file will be moved into the completed folder.

When the file listener is redeployed in higher environment and updated the credentials in repository rule as a post deployment change, the file is getting processed once uploaded but not moved into completed folder, eventhough restarted the File listener after re-deployment.

For fixing this issue, every time we have to request for a server restart after which it works fine.

Why environment restart is required for a re-deployed File Listener when updated the repository rule with source location path name, for moving the processed files into the completed folder?