HI @rakesh Need your comments on this and Any ETA if this needs to be implemented.

@rakesh to elaborate, the Company Person job fails without any information explaining why it failed. In this case, one record had a null value in the Email field causing the entire job to fail.

But because there was no log information to be found, I had no idea why it failed, forcing me to open a support ticket to find out the cause. it took six days for Gainsight to get back to me with a root cause and then I was told that engineering said this is expected behavior.

Anytime there is a failure, error, what-have-you, admins need to be able to have access to this information without having to log a ticket, wait for L1 to acknowledge it, wait again for L1 to decide it needs to be escalated to L2, wait for L2 to acknowledge it, wait for L2 to come back to me saying it’s expected behavior, wait for L2 to escalate to engineering when I contest the response, etc. etc. 

Wait. One bad record flunks the entire job? That’s unexpected to me.

Also, I concur that empowering GS Admins with error information here has big impact. Many of us (and most certainly @darkknight) have the knowledge, expertise and willingness to self-research and self-remediate failures. Efficiency and scale for virtually everyone is gained by putting this information in the hands of the admin.

@matthew_lind yeah I realized after I posted that comment it was only one record picked up by the job (but I couldn’t edit the comment - I hate that missing capability) but regardless, there was no way for me to know what record failed or why.