Monitoring
If your data sync configuration has failed, here are a few items of consideration:
Have your credentials changed in either the source or target (e.g. expired password)?
Is your sync key unique in your source and target?
Is the configuration entered in the [Cinchy].[Data Sync Configurations] table?
If source is a file, does it exist at the specified location?
Cinchy Tables
When running a datasync interactively, the output screen will display the result of the job on the first line, there are two (2) potential outcomes:
Data sync completed successfully
Data sync completed with errors (see <temp folder>for error logs)
If the data sync runs on a schedule, there are two (2) tables in the Cinchy domain that can be reviewed to determine the outcome:
Execution Log Table - this is where you can find the output and status of any job executed
Please note, you can see when the job ran by the Create timestamp on the record. (Display Columns -> add Created column to the view)
Execution Errors Table - this table may have one or more records for a job that failed with synchronization or validation errors
Execution Log Table Schema
Execution Error Table Defined
Tip
To automatically check if the job was successful, you have three (3) exit codes that can be checked for the job:
0 - Completed without errors
1 - Execution failed
2 - Completed with validation errors
Sample Code
Logs
The syncdata command will use the folder, indicated after the -d parameter in the command line, to create and store temporary files. If the data sync is successful, all the temporary files are automatically purged. However, if there is an error the following CSV files will exist:
ExecutionLogID_SourceErrors.csv
ExecutionLogID_SyncErrors.csv
ExecutionLogID_TargetErrors.csv
For more information on detailed error messaged click here if required.
Last updated