Sonataflow reuses PgSQL database created by Backstage operator including the Secret which is a part of Backstage CR instance containing generated PgSQL DB credentials.
The problem is that if user recreates Backstage CR, the Secret (along with DB server) is recreated and credentials regenerated while Sonataflowplatform CR is still the same and tries to use "old" credentials, and fails. The workaround is re-creating Sonataflow's pods.
The decision to make is how to avoid or make the reason and way to solve it more clear.
Possible options:

• better document it (OK for start)
• make Backstage CR own the Sonataflow Platform (not complex, good fit for "easy to install" option)
• consider shared for cluster between Sonataflowplatform instance with own DB (more complex but more prod friendly, combining with dedicated PgSQL DB)