Tim, its possible you’re setting a value to a join field that’s causing the issue.
In your “Set” you’re setting a connection field value to the the value of the Pipe status response. You’re effectively overwriting the connection field. I’d recommend creating a new field you can use just for this purpose.
The reason this might be happening is the way the pipe runs.
The record rule attempts to set all the values, if one of the values is a “Pipe Value” it will then trigger the pipe. This is perhaps not the best way to do it and we’re looking into running the pipe regardless of values being set.
One last thing I would try is setting the (Table ID) field to a custom value of Table ID vs the dropdown you’re using.
Please let me know if this works for you or you have any traditional questions.