Introduction
Use this guide to troubleshoot cases where the Divert Confirm File is not being picked up by WMS. This article focuses on verifying file generation, file location, naming, and WMS pickup behavior so you can restore the file flow and confirm that out/diverti.rsc is being processed correctly.
Issue description
The Divert Confirm File is not being picked up by WMS. The expected file, out/diverti.rsc, is now being picked up by WMS.
Signs
WMS does not detect the divert confirmation file.
The file is not present in the expected output directory.
The file name or extension does not match the WMS pickup configuration.
File permissions or transfer timing prevent WMS from reading the file.
Basic troubleshooting steps
Checklist:
Confirm the divert confirmation process completed successfully.
Verify that the file is being written to the expected directory.
Confirm the file name is exactly out/diverti.rsc, or the name required by your WMS configuration.
Check that WMS has permission to access the file location.
Review recent changes to file paths, interfaces, or polling schedules.
Diagnostic tools and resources
WMS interface logs
File system directory listing
Integration or middleware logs
Pontem operational data or system monitoring views, if applicable
Advanced troubleshooting steps
Step 1: Verify file creation and path
Confirm that the divert confirmation file is created in the correct output location. If the file is generated in a different folder, update the configuration so WMS can monitor the correct path.
Step 2: Confirm file naming and extension
Check that the file name matches the WMS pickup rule exactly. Some systems require a specific file name, extension, or case-sensitive pattern. Validate that out/diverti.rsc is the expected name in your environment.
Step 3: Review WMS pickup configuration
Verify the WMS polling schedule, watched directory, and interface settings. Make sure the pickup service is running and that no filters or exclusions are preventing the file from being processed.
Step 4: Check permissions and file locks
Confirm that the WMS service account has read access to the file and directory. Also check whether another process is locking the file before WMS can pick it up.
Step 5: Review logs for interface errors
Inspect application, middleware, and WMS logs for errors related to file pickup, parsing, or transfer failures. Use the timestamp of the file creation to narrow the search window.
Contact support
If the issue continues after completing the steps above, contact Fidus Global support with the following details: file name, directory path, WMS version, recent configuration changes, and any relevant log excerpts.
Additional resources
WMS interface configuration guide
File transfer and directory monitoring documentation
Pontem monitoring and operational visibility resources
Conclusion
When the Divert Confirm File is not being picked up by WMS, the most common causes are path, naming, permission, or polling configuration issues. Verifying out/diverti.rsc, checking logs, and confirming WMS pickup settings will help restore normal processing.
Disclaimer
Use this guide as a general troubleshooting reference. Your site configuration, WMS platform, and integration design may require additional steps. Follow your organization’s safety and change-control procedures before making system changes.