We use workflow status to move content through our subbing queues and to indicate key stages such as Draft, various review states, and Published.
The problem
At times, content is published using the Publish button, but the workflow status is not updated to reflect this. When the workflow status remains incorrect, it creates downstream issues - particularly in planning views and queue management - because the content appears to still be in an earlier stage.
Why this happens
We understand that Arc customers configure workflows differently, and that workflow status updates are currently a manual step for users.
Proposed improvement
From our perspective, it would be highly valuable to support a customisable trigger (optional and configurable by Admins or developers) that automatically updates an article’s workflow status - such as setting it to Published or another selected state - when the Publish function is used.
Value
This would reduce human error, keep workflow status aligned with actual publication state, and improve the reliability of queues and planning views without forcing a one-size-fits-all workflow across customers.
Toni East
I'm with the crowd, let's do it!
This change would close a significant gap in our publishing workflow. At present, a story can be published in Composer but still appear as “in progress” because the status dropdown hasn’t been manually updated. That creates confusion, duplication of work, and the real risk of a subeditor re‑opening a story that’s already been edited and pushed live.
Makes sense
This change will allow us to be faster, and reduce margin for error - very keen thanks.
This would be a massive help - and would rule out a very common human error that currently hinders production.