volume_ids cached when hitting the /droplets end point

I have a particular use-case where I rebuild the droplet every night, including detaching all volumes and attaching new ones. I notice several issues.

1) Occasionally the /droplets endpoint caches the volume_ids and shows an output despite those volumes not existing
2) Sometimes, I've created new volumes and attached them to the droplet, but the /droplets endpoint will show me the old ID.