Hi @pikut, I couldn’t reproduce the issue based on the screenshots you sent; I think it’s mainly because it’s still not a clean screenshot (it still contains your overlays from Studio).
Even so, the cell targeting should still work: if you reference the target cell via its column name (as is the case in my screenshot) vs. column index, ghost columns shouldn’t be an issue. Moreover, you can also specify a row contains (similar to an anchor with a non-table-cell target) to make sure you have the correct row as well.
Also, we’re close to deploying a new AI Model which has been trained a larger tables dataset, so the ghost columns issue might disappear. We could test this if you send a clean screenshot (no overlays).