# Google Sheet Publisher Issue - Somehow DB entities for publisher got into problem state **URL:** \ **Category:** Support\ **Tags:** odk-aggregate\ **Created:** [February 18, 2018, 9:44am UTC](https://forum.getodk.org/t/google-sheet-publisher-issue-somehow-db-entities-for-publisher-got-into-problem-state/11862 "2018-02-18T09:44:57Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![esurface](https://getodk.b-cdn.net/letter_avatar_proxy/v4/letter/e/977dab/32.png) [@esurface](https://forum.getodk.org/u/esurface)\ **Post date:** [April 22, 2019, 10:10pm UTC](https://forum.getodk.org/t/google-sheet-publisher-issue-somehow-db-entities-for-publisher-got-into-problem-state/11862/19 "2019-04-22T22:10:23Z")
We are running into the same issue which explains the high charges in our other [ticket](https://forum.getodk.org/t/odk-1-on-gcp-app-engine/19189). The crash is happening so often that I can't even open the published forms pane for the particular form on the ODK Aggregate server. I believe the part of your solution that fixes this is to 'remove the oldest duplicated row'. Is that all that is needed for the fix? This will need to be done in the GCP DataStore. Also, when we publish data in the future, what can we do to prevent the issue from happening again? Thanks! Erik --- _[View the full topic](https://forum.getodk.org/t/google-sheet-publisher-issue-somehow-db-entities-for-publisher-got-into-problem-state/11862)._