# dagster-support

Nathan Skone

08/22/2022, 8:47 PM
Hello everyone. We are having trouble with some asset jobs. We deployed a second workspace and job with assets identically named to another workspace/job, and it seems to have broken dagit. It appears that assets need a globally unique name, but we did not know that beforehand. We redeployed the second job with new asset names, but Dagit still sees the original asset names despite clicking “Reload” on the workspace in Dagit. How can we fix Dagit in this situation?
🤖 1

Adam Bloom

08/22/2022, 8:59 PM

Nathan Skone

08/22/2022, 9:28 PM
@Adam Bloom Seems to be related, yes
We have worked around this issue by wiping out our dagster postgres instance. This means we lost all our job history.


08/23/2022, 8:19 PM
Hey - sorry you ran into this. Wiping the run history was definitely the quickest fix, but looking into ways in which that can be avoided in the future s.t. we don't punish you for this mistake so heavily. At the least, we will be communicating more heavily that asset keys need to be globally unique

Nathan Skone

08/23/2022, 10:47 PM
@chris Thank you for the response Chris. This is definitely a footgun that deserves to be caught ahead of time, or at least be much more fixable.