it would be safe to reprocess automatically if there were only one transaction (sale or whatever) in the file, and the processing is occurring relatively infrequently or the failure is caused by a Communication error or similar which does not occur on the next round. In most other circumstances it is not such a good idea. The file may contain data which was processed or the issue may be one which will repeat at every attempt until it is fixed.
Where some data has been processed there is a risk of duplication. TransPost does try not to duplicate transactions but sometimes there is an adjustment at the MYOB end and TransPost fails to recognise that the transaction is one that has already been processed. If the file were to be reprocessed automatically then a transaction that went in the first time might be duplicated. If the import is happening say every couple of minutes that can add up to a lot of duplicates before anyone realises. Deleting transactions can only be done manually in MYOB, one at a time.
If the issue is a problem that requires data intervention either in the file or in MYOB to resolve then it will keep failing and on a frequent schedule, if automatically resubmitted, that would add up to a very long log and masses of 'unprocessed data' files.
Finding Unprocessed data
When some or all of a file is not processed, the unprocessed data will have been copied to the daily sub-folder of the Unprocessed Data sub-folder of the logs folder. (Click Explore Logs on the Import tab to go to the log folder.) The unprocessed data file is exactly the same as the original input but with the processed data lines removed. It can be processed through the same mapping.
If you are running on automatic, using the TransPost Service, check for the presence of 'Unprocessed Data' files. If they exist you may have an issue to fix or a simply a file to reprocess. If not relax, all is well.
To simplify this, from release 3.3.1 (scheduled for release April 2016), there will be an additional log file in the log file folder (Explore Logs) called TransPost Import Errors.csv which will ONLY contain errors. It will not be created until there is an error. While it continues to not exist all data has been processed successfully (but possibly with warnings).
When it appears you deal with it and archive or delete it. You can then relax until the next time it appears.
If a transaction fails because the data is invalid, e.g. customer or item number not found in MYOB, there has to be some intervention before its worth trying again. On the other hand there are failures which relate to temporary or even momentary lack of access to the company file. Where we have identified the error messages which represent such circumstances, the latest releases of TransPost (3.3.1 and later) will pause for a few seconds and resubmit the transaction before moving on to the next transaction.
At present these circumstances include:
- Some types of AccountRight Live communication error
- In classic Myob, error codes which indicate that the MYOB program is unavailable or the company file is locked or similar, or the ODBC driver thinks it is.