Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring file listener error recovery

Updated on April 6, 2022

You can automate how your file listener recovers files if an error occurs. In the file listener rule form, specify the processing that occurs at run time when requestors that are based on the file listener encounter errors. For example, you can rename files with the file extension .err so that you can easily identify the files that the file listener could not process.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Integration-Resources category, and then click File Listener.
  3. Click the file listener for which you want to configure error processing.
  4. Click the Error tab.
  5. To leave files that contain errors in the Work subdirectory for recovery purposes, in the Error recovery section, select Attempt recovery?.
    When selected, file listener processing might create many instances of the Log-Service-File class to aid in debugging, which might affect system performance.
  6. To specify the maximum number of times the system attempts recovery, in the Max recovery attempts field, enter 0 or a positive integer.
    The default is three recovery attempts.
  7. In the Cleanup section, in the File operation field, select whether to rename or delete files with errors.
    If you select Rename, files are moved into the completed subdirectory with the extension specified in the File extension field. Files are moved only after all recovery attempts fail.
  8. In the File extension field, enter a file type extension to append to renamed files, for example, .err.
  9. Click Save.
  • Previous topic File listener error handling and debugging
  • Next topic Best practices for processing files using the file listener

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us