# contributing


11/03/2022, 2:50 PM
Hi all, I just used the export/import configuration yaml feature (first screenshot). I exported the yaml from a GrowthBook instance and imported it in another, fresh one. The built of both instances is identical (Build: 2b811d1 (2022-11-02)). The technical environments of both GrowthBook instances are also identical. When importing the exported yaml, a client error occurs (see the second screenshot). For me it looks like the importer expects a "Jupyter Notebook Query Runner", which was never configured in the instance exported from. As an additional effect of the error, I now can't manage and delete the broken data sources any more. Is this a bug? If yes, how can one either repair or get rid of the data sources? FYI: @adventurous-dream-15065


11/03/2022, 5:28 PM
Hi Peter - can you dm me your config.yml?


12/12/2022, 2:26 PM
Ahoi, we found the error. For some reason the imported data sources were stored without the field “settings”. This lead to a couple of downstream issues whenever the frontend requested the settings, e.g. for metrics creation. I don’t know whether this is a bug, maybe you want to look into it. We solved the issue by deleting the affected datasources using your very instructive RESTful interface (DELETE /datasources/<id>).