If you are not already using the add to update set utility, I highly recommend adding it to your instance. Decision tables can be tricky to capture if they are not already in your update set. The schema alone for the decision table comprises several different references. As a test, I made a new decision table in a global update set and used the add to update set utility to add the decision table record to my current update set "test." When I view my updated set, there is only one record; this is an issue as decision tables are made of several components. A solution for this could be to edit the value in the decision table, save it, and publish it again, and then it would be captured. If the decision table is currently being used as a flow or subflow, it could cause the branches to appear deleted, leading to the need to recreate whatever logic is used in the decision table. The better solution would be to put the decision table in draft mode and then change the description or title. Once the change has been made, save and publish the decision table. When you look at the "test" update set, you can see that all the components have been captured. Let me know if that helps!
 
 
 
