SmartMover V2b:Issues: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[SmartMover V2b|← SmartMover V2b]] | |||
{{CustomTOC}} | {{CustomTOC}} | ||
SmartMover known issues. | SmartMover V2b known issues. | ||
==Build 1.0.1.21== | ==Build 1.0.1.21== | ||
| Line 15: | Line 16: | ||
[[Category:Issues]] | [[Category:Issues]] | ||
[[Category:SmartMover]] | [[Category:SmartMover V2b]] | ||
Latest revision as of 01:07, 8 December 2018
SmartMover V2b known issues.
Build 1.0.1.21
Released August 2009
If a request takes too long to process and times out and the same request is sent again, both requests are still processed by the server and the CASS and NCOA reports will log both the timed out and the subsequent request. This will leave you with an inflated record counts in your CASS and NCOA reports if any timeouts occur.
- Work-around
- Manually track any timeouts and adjust the CASS and NCOA reports accordingly.
- Solution
- A solution for this issue will be released in the next version.