Automated SP_WhoIsActive SQL Activity Capturing Issue
It appears from the Primary Key name that you are running Adam Machanic's sp_WhoIsActive and storing the result in a table.
If that is the case, the warnings are normal and caused by the options you set when calling sp_WhoIsActive. The Primary Key violation is what is causing the job to fail.  Take a look at the definition of the primary key.
I believe you will find that the Primay Key needs to be changed in order to insure uniqueness.
In my implementations for this I leave the table as a heap and do not define a primary key on this table. I only keep a few days of data in the table and do not use it for replication.
Here is an article on how to implement it:
Brent Ozar Implementation of sp_WhoIsActive