Closed belkassaby closed 1 year ago
@belkassaby I did not have this error occur on dev.
This might be due to a corrupt phenopacket that you had previously created on sqa (the old instance) i would clear up all you phenopackets in sqa and then you could try once more to see if that happens on sqa UPDATE: that was the case indeed: there was a phenopacket that had been created previously on the datastore with a theraapeutic regimen that didn't have either the ontoologyClass or the externalReference property. I just deleted it. You should be able to see your other phenopackets.
@belkassaby Logoff and login are working fine on both dev and sqa sites this morning. Problem is solved.
Therapeutic regimen UI allows the saving of corrupt phenopackets that then will block the reloading of the previously created phenopaket