Fatal Error and scheduler is not creating for some post

Hello @gwlwp ,

Thank you for reaching out to us.

We’ve received similar errors like this in the past and our developers have since released a fix for this. Can you confirm if your MailPoet Plugin has been updated to the latest version (Version 4.3.1)?

Looking forward to hearing back from you.

Have a great day!

Hi there @gwlwp,

We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Still, we are getting the same error with update plugin also.

[07-Mar-2023 09:36:02 UTC] PHP Fatal error:  Uncaught MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException: A new entity was found through the relationship 'MailPoet\Entities\SendingQueueEntity#task' that was not configured to cascade persist operations for entity: MailPoet\Entities\ScheduledTaskEntity@9764. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}). If you cannot find out which entity causes the problem implement 'MailPoet\Entities\ScheduledTaskEntity#__toString()' to get a clue. in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php:45
Stack trace:
#0 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(1827): MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException::newEntitiesFoundThroughRelationships()
#1 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(138): MailPoetVendor\Doctrine\ORM\UnitOfWork->assertThatThereAreNoUnintentionallyNonPersistedAssociations()
#2 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityManager.php(171): MailPoetVendor\Doctrine\ORM\UnitOfWork->commit()
#3 /wp-content/plugins/mailpoet/lib/Doctrine/Repository.php(118): MailPoetVendor\Doctrine\ORM\EntityManager->flush()
#4 /wp-content/plugins/mailpoet/lib/Logging/LogHandler.php(65): MailPoet\Doctrine\Repository->flush()
#5 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(18): MailPoet\Logging\LogHandler->write()
#6 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(114): MailPoetVendor\Monolog\Handler\AbstractProcessingHandler->handle()
#7 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(218): MailPoetVendor\Monolog\Logger->addRecord()
#8 /wp-content/plugins/mailpoet/lib/Cron/Daemon.php(63): MailPoetVendor\Monolog\Logger->error()
#9 /wp-content/plugins/mailpoet/mailpoet-cron.php(61): MailPoet\Cron\Daemon->run()
#10 {main}
  thrown in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php on line 45


[07-Mar-2023 09:37:02 UTC] PHP Fatal error:  Uncaught MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException: A new entity was found through the relationship 'MailPoet\Entities\SendingQueueEntity#task' that was not configured to cascade persist operations for entity: MailPoet\Entities\ScheduledTaskEntity@9790. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}). If you cannot find out which entity causes the problem implement 'MailPoet\Entities\ScheduledTaskEntity#__toString()' to get a clue. in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php:45
Stack trace:
#0 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(1827): MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException::newEntitiesFoundThroughRelationships()
#1 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(138): MailPoetVendor\Doctrine\ORM\UnitOfWork->assertThatThereAreNoUnintentionallyNonPersistedAssociations()
#2 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityManager.php(171): MailPoetVendor\Doctrine\ORM\UnitOfWork->commit()
#3 /wp-content/plugins/mailpoet/lib/Doctrine/Repository.php(118): MailPoetVendor\Doctrine\ORM\EntityManager->flush()
#4 /wp-content/plugins/mailpoet/lib/Logging/LogHandler.php(65): MailPoet\Doctrine\Repository->flush()
#5 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(18): MailPoet\Logging\LogHandler->write()
#6 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(114): MailPoetVendor\Monolog\Handler\AbstractProcessingHandler->handle()
#7 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(218): MailPoetVendor\Monolog\Logger->addRecord()
#8 /wp-content/plugins/mailpoet/lib/Cron/Daemon.php(63): MailPoetVendor\Monolog\Logger->error()
#9 /wp-content/plugins/mailpoet/mailpoet-cron.php(61): MailPoet\Cron\Daemon->run()

Please fix this issue.