>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3218315. --> Reported by: [rex.barkdoll](https://www.drupal.org/user/1808716) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As we're doing testing on our website, we're creating and deleting content and we've run into the issue where we've deleted something while there's a notification pending to be sent out. This causes an issue in Cron (its actually in Push Framework's queue i think) and that prevents it from running until we run the edel commands to clear out the bad notifications.</p> <p>The following edel commands clear out everything and fix the problem, but they also lose all the logs of notification data we might want to keep.<br> drush edel danse_notification_action<br> drush edel danse_notification<br> drush edel danse_event</p> <p>Is there some sort of way push framework can test that the content still exists and, in the event that it doesn't, fail gracefully with a notice rather than the full error stack that happens now?</p> <p>I imagine we still want the full error available in some way, but I'd also like for cron to be able to still execute successfully. </p> <p>Additional feature requests with this would be the ability to individually delete bad events from the queue so we can clear them out piecemeal rather than in totality.<br> This could be through the UI or command line.</p> <p>Thank you!</p>