Every bridge row has a History button, and the run count on the row is clickable too. Both open the recent run history for that one bridge.
What run history answers:
- Has this bridge run at all since I created it?
- Who was synced, and when?
- Which destinations accepted the contact and which rejected it?
- What exact error did a failing destination return?
Why it beats the full log:
The Activity Log covers everything WP Sync has done across every bridge. When you are debugging one automation, that is a lot of noise. Run history is already scoped to the bridge in front of you, so the last few runs are the first few rows.
Reading an empty history:
An empty history is itself a diagnosis. It means the bridge has never fired, which points at the source rather than the destination. Check that the bridge is enabled, that the source really is a source, that a new contact was added after the bridge was created, and for push sources that the webhook URL was pasted into the other app.
Run history and dry runs:
A dry run is a preview, not a run, so it does not create history entries. If you want a real entry, add a genuine contact to the source and click Run Sync Now.
What to do with a failure:
Read the per destination message. Credential problems name the app and usually mention authorisation. A rejected write often names the field the destination insisted on, which is normally fixed with a fallback value in that destination's field mapping. If the message is not clear, open the Diagnostics tab and use the support report.