If an archive job is running and the node is restarted, the Archive Run State remains "Active"
Release or Environment
What happens is when the node is restarted mid archive there is no hook to end the current Archive run to mark it as complete so it gets stuck in Active.
It won't affect future archiving runs.
It's ok to manually change those to completed.
If customer comes back and they want us to change from Active to Completed and Message to Completed archive
You will need a Change to do this from the backend as the UI does not allow.