Request chaining cross linking?

I have two HTTP calls that I’ve duplicated into two groups. Each group is for the same API endpoint but a different input to return a different service. The first call requests the ID based on the service name, and the second uses response chaining to pull the service details with the retrieved ID from the first call. This works as expected.

I duplicated these two calls so I could do the same process with a second service name. My problem is that for some reason, the service detail call of second set pulls the first service details. Like it’s somehow connected to the original request chain and not the second.

EG:

I’m using a JSONPath sum function to add an offset in the response chain which is why the ID and the service detail call are slightly different, but it works in the first example.

Call 1a - returns ID 30400

Call 1b - returns service details for service 330400

Call 2a - returns ID 30401

Call 2b - returns service details for service 330400(not 330401 as expected)

Note that if I enter the ID manually into the 2b URL, it returns the expected service details, so it’s definitely something to do with that response chain. I’ve double checked that I’m referencing the second call for the request chain, and I rebuilt call 2b from scratch to see if it was something odd with the duplication process, but no dice.