Not able to extract the details who deleted the external account from Audit log

[#1]

There is an external account which is deleted accidentally. We are tried to get the details of operator , timestamp and action from the audit log.  We did not able to extract the required entry from audit log which will give the clear message of deletion.

Please help and share ideas how we can manage. 

[#2]

Hi @pghoshchoudhury ,

In Adobe Campaign Classic, deletion of External Accounts is not always fully captured in the Audit Log.

The Audit Log mainly records specific operations such as updates and selected system actions. However, when an External Account is deleted (Administration → Platform → External Accounts), the system does not consistently log:

• Operator (who performed the action)

• Exact timestamp

• Explicit “delete” action entry

Because of this limitation, it is possible that the deletion will not appear with a clear message in the Audit Log, even though the account was removed successfully.

What can be checked as alternatives

• Operator activity: Review operator login history or admin activity around the suspected time.

• Application / server logs: Check web and workflow server logs (nlserver web, nlserver wfserver) for any related admin operations during that timeframe.

• Package / deployment history: If any package import or instance maintenance occurred, the External Account may have been removed as part of an overwrite.

• Database backup comparison: If backups are available, compare the xtk:externalAccount table to confirm when the record last existed.

Conclusion

Adobe Campaign Classic does not guarantee full traceability for External Account deletions. Once deleted, it may not be possible to reliably identify the operator or exact timestamp using the Audit Log alone.

Recommendation 

• Limit delete permissions for External Accounts to a small group of administrators.

• Maintain documentation or change records for admin-level actions.

• Periodically export or back up External Account configurations.

  

  Thanks,
  Giriprasath B