--refresh-dependencies doesn't pull in changed dynamic dependencies

During develop we have some dependencies we pull in with a +. When using --refresh-dependencies should Gradle pull in updated dynamic dependencies? Or does the TTL settings for the gradle cache still apply (24 hours by default)?

I only ask because refresh-dependencies does not actually result in getting the newest dynamic dependency so trying to figure out what the behavior is supposed to be.

Actually since 4.10 the only way to get gradle to pull in updated dynamic dependencies is to wait 24 hours (even if we set the TTL to something much lower), or delete the caches.

What is the correct behavior for --refresh-dependencies and is anyone else having this issue?

Using --refresh-dependencies should result in the dynamic dependencies being re-resolved from the configured repositories. Are you able to reproduce the issue with a minimal example build (no extra plugins, etc)?