Troubleshooting interaction history
If you experience problems when working with interaction history, use the following tips to troubleshoot and solve the most common issues.
- Interaction History component processes data longer than expected
The Interaction History component in a strategy takes more time to process data than expected.
- pyApplication and pyApplicationVersion properties are not captured in the interaction history
When running a data flow run through a service SOAP rule, the pyApplication and pyApplicationVersion properties are not captured in the interaction history. This issue can lead to unexpected data flow results or the interaction history records not being saved.
- Values of the pxOutcomeTime property are not unique in the Oracle database
The type of the pxOutcomeTime property in the PR_DATA_IH_FACT table is by default set to DateTime. In the Oracle database, any records that are written into the PR_DATA_IH_FACT table of the interaction history are stored with one-second precision.