CB Core Fields Ajax is just that, ajax. You're redirecting the ajax endpoint and causing it to break. CB Core Fields Ajax always has and always will fire profile update triggers as it's to signify the profile has been updated (this is expected behavior).

Your redirect action needs to take all of this into consideration. Probably the easiest is to just ensure the output isn't raw. This can be done with the below condition.

[get_format] Not Equal To raw

Another option is to absolutely be sure its a profile edit save as follows.

[get_view] Equal To saveUserEdit

Another option is to use the onAfterUserProfileSaved trigger as it is only fired specifically for the profile edit save, but only contains the newly updated user object (so won't be of much use if you need to condition new values against old).

is there any where I could read about the auto action triggers?

At this time all we have is the below reference tutorial for trigger usage, but it's out of date. A lot of the triggers however still exist.

www.joomlapolis.com/support/tutorials/120-api-usage/18358-using-cb-triggers

it will be great if we have the list of triggers and a short explanation?

All triggers available are in the CB Auto Actions dropdown. The name of the trigger is meant to be self explanatory as best as possible. There's no description list for triggers at this time.