Thanks for your suggestion. The good news is that it now recognizes the newly added item and does change the color. The bad news is that it is changing to the default severity level of 0 or "N/A" which is #EFEFEF. If I add another item to the same subcategory (A2.1, A2.2) there is no color change; however, if I add another item to a different subcategory (A2.1, A3.1) , the PREVIOUS item that was just ADDED changes to the correct color. EDIT and DELETE are still working correctly. I welcome any other suggestions that you may have.

Thank you for your suggestions. Yes, I was wondering if it relates to timing. I've waited for several hours and also a couple of days to see if it eventually updates the color on the newly added item. It does not so I'm thinking it isn't a timing issue? It will only update the newly added item's color if I add another item to a different subcategory. It's like it is one previous step/version behind.

I included an itemCount alert that shows the call is getting the correct number of items in the list. I also added your suggestion and the alert states that it is ready. The itemCount alert appears prior to the “ready” alert. If it recognizes items that have been edited and also deleted and also is receiving all item in the list, then I’m really confused why it doesn’t see the very latest newly added list item. I could post the JavaScript if that would help?