This is a fix request for the article content publishing.scheduled_operations field
Current State:
When an article is scheduled in composer and then the story is fetched via the content api (fetch a single document, fetch a list of stories, fetch a story,..) the resulted ans shows the correct publishing.scheduled_operations.publish_edition state.
But if the article is unscheduled the publish_edition state remains in the ans - even if it's shown correct in composer. This state does only change when the article is saved again.
So before saving the article the ans does not represent the correct state.
Expected Results
The ans does always represent the current article status. That also includes the publishing.scheduled_operations property. When the scheduling is removed in composer, the state should not be shown in the ans or marked as “removed”. It should not be necessary to save in composer again to fix the state.
Steps to Reproduce
Create a random article in composer, schedule it in the future and fetch the ans by the content api. The publishing state is correct.
Then unschedule the article in the composer with the “unschedule” Button and fetch the ans again. The publishing state is incorrect even after a few minutes.
Save the article and fetch the ans again. The publishing state is correct.
Daja
