For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.
This topic explains how to monitor the data synchronization log.
If table events are not logged in the Data synchronization log as expected, you can check the data synchronization setup for your message or outbound web service action.
If logged events in the data synchronization log are not processed to the outbound queue, you can:
Check if processing the data synchronization log is set up correctly.
Test the data synchronization log processing.
If processing the data synchronization log does not run at all, the batch server can be down.