Skip to content

fix: Add explicit Adobe MID resolution logging#31

Merged
denischilik merged 2 commits into
mainfrom
fix/adobe-media-mid-success-log-main
Apr 27, 2026
Merged

fix: Add explicit Adobe MID resolution logging#31
denischilik merged 2 commits into
mainfrom
fix/adobe-media-mid-success-log-main

Conversation

@denischilik
Copy link
Copy Markdown
Contributor

Background

Troubleshooting MID resolution in runtime logs is currently ambiguous because only error output is explicit.
This change adds clear success-state logging for Adobe Media MID retrieval and persistence.

What Has Changed

  • Added explicit success log when Adobe MID is retrieved successfully
  • Added explicit log when MID is empty (no error, but no value)
  • Added explicit log when integration attributes are updated with MID
  • Kept existing error logging intact for timeout/failure scenarios

Screenshots/Video

N/A

Checklist

  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have tested this locally.

Additional Notes

This update is diagnostic-only and does not change SDK behavior.

Add success and empty-MID log lines in syncId so runtime logs clearly distinguish successful ECID retrieval from timeout/error cases.
Add a dedicated log line when Adobe Media updates MID integration attributes so support can confirm the exact point MID is persisted in runtime logs.
@denischilik denischilik merged commit e55a5da into main Apr 27, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants