RELATED IDEAS
Log the SysId of the entity and user in the context when there is an internal/unexpected error occur
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Administrators and developers dealing with production incidents |
What impact would it make? |
Ensure data integrity after the issue is addressed. |
How should it work? |
Several instances of the internal error or unexpected errors occurred, especially when there is error in registering the event in the listener queue, we lose the context of the entity that ran in to error and user who's action triggered the event. Log message of error along with entity's sysId and user name will help us trace back to the change. Using that information, we can reprocess the custom extensions only for those entities to ensure system's integrity is maintained. |
Why is it needed? |
Without that information, we are forced to do massive query of data and scan through the field history to figure out which entities were updated during the down time and inevitably process all those entities irrespective of if they were run in to error or not. |
Additional feedback, background or context:
We had a major incident where Entity Update events were not published/registered in to entity listener queues. We see the error "Failed when publishing event 'EntityUpdated'" 1072 times in the logs but we have no clue which entities' events were failed to publish.
We need to reprocess those entities.
Without the entity and user information, we are now trying to scan through all the updates happened on that day, scan the field history of each entity and reprocess every entity that was updated on that, irrespective of whether that entity was affected by the error or not.
Having Sys_Id and user id in that error will give us clearly which of those 1072 entities we should focus on.
