Thanks for raising this with such detailed steps to reproduce!

The bugs you've raised under With EmbargoExpiryFluentExtension definitely warrant looking in to and resolving. We need to make sure that the messaging is clear (for each locale respectively) and that the correct jobs are created and maintained.

I don't think we would spend any time on Without EmbargoExpiryFluentExtension, as the expectation would be that you do use the EmbargoExpiryFluentExtension if you have Fluent installed. I'm going to keep a record of them here, but I'm going to remove them from the Issue description so that the focus is on With EmbargoExpiryFluentExtension.

Originally in the Issue description:

Without EmbargoExpiryFluentExtension (https://github.com/silverstripe-terraformers/silverstripe-embargo-expiry/blob/master/docs/en/fluent-support.md)

How to reproduce

• create a page in locale1 and set publish date in future
• localise page in locale2; you can see warning of emabrgo and same date as in locale1
• run dev/tasks/ProcessJobQueueTask (after the set time)

Expected result

• page published in all locales

Actual result

• page in locale1 still in draft
• page in locale2 published

DB result

• SiteTree_Live record created
• SiteTree_Localised_Live record created for locale2, no new record for locale1

@AljosaB could you please also let us know what version of Embargo & Expiry this was experienced on?

@chrispenny I somehow missed your response. As instructed I always test things on latest clean SS installation (in this case SS 5.2.x) and only thing added extra was embargo-expiry v2.0.0