# Cannot resolve secret references **URL:** \ **Category:** Need Help\ **Created:** [June 21, 2022, 5:11pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663 "2022-06-21T17:11:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![chuckwondo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/chuckwondo/32/463_2.png) [@chuckwondo](https://community.doppler.com/u/chuckwondo)\ **Post date:** [June 21, 2022, 5:11pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/1 "2022-06-21T17:11:11Z")
When I attempt to reference one secret from another secret, I get an error when I attempt to save my changes. For example, if I create secrets X and Y, and I reference X from Y using the syntax ${X}, when I attempt to save my changes, I get the following error: ```nohighlight The secret "Y" cannot resolve the reference ${X}. ``` However, I can reference any _predefined_ name without issue, such as ${DOPPLER\_ENVIRONMENT}. Is there something I need to configure to allow references to my own secrets? ---
**Author:** ![chuckwondo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/chuckwondo/32/463_2.png) [@chuckwondo](https://community.doppler.com/u/chuckwondo)\ **Post date:** [June 21, 2022, 9:42pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/2 "2022-06-21T21:42:04Z")
As far as I can tell, this appears to be related to repurposing the starter/example project, which defines some example secrets. I used the example and simply renamed some secrets and deleted the extra secrets I didn’t need. When I attempted to reference one secret from another, I ran into the error above. However, when I created a completely new, empty project, with no pre-populated example secrets, I did not encounter the error above. ---
**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\ **Post date:** [June 22, 2022, 4:30pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/3 "2022-06-22T16:30:40Z")
Hi @chuckwondo! Just wanted to chime in here after our discussion in a separate support ticket to note that I wasn’t able to reproduce this on the example project that’s included in new Workplaces. That starter project is just a normal project, so it should behave like any other project. If anyone else runs into this issue though, please feel free to chime in and we can take a deeper look to see what might be causing that behavior. Regards, -Joel ---
**Author:** ![noblesse](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/noblesse/32/389_2.png) [@noblesse](https://community.doppler.com/u/noblesse)\ **Post date:** [July 8, 2022, 5:09am UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/4 "2022-07-08T05:09:09Z")
Got the same error today. Not able to reference another secret in the same project env ---
**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\ **Post date:** [July 20, 2022, 5:17pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/5 "2022-07-20T17:17:00Z")
Hi @noblesse! Welcome to the Doppler Community! Thank you for reporting this! We’ve actually run into this a couple times internally and have been investigating. We believe we’ve found the cause of the issue and are working on a fix for it. It has to do with when a project is renamed. I’ll post again once the fix is deployed. Regards, -Joel ---
**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\ **Post date:** [July 28, 2022, 2:38pm UTC](https://community.doppler.com/t/cannot-resolve-secret-references/663/6 "2022-07-28T14:38:48Z")
Okay, we just shipped a fix that should solve this! Please post again if you still run into it!