I have discoverd instances in conversation_parts where the conversation_part.status is in a snooze state even if the part_type is a comment type. How is this possible, because according to this article (https://www.intercom.com/help/en/articles/6564538-snooze-a-conversation) 

“If you send a reply message in a 'snoozed' conversation that's assigned to you, it will not automatically 'unsnooze'/reopen the conversation.”

“If someone else sends a reply, adds a note, or updates an attribute in a 'snoozed' conversation assigned to you, it will be automatically 'unsnoozed'/reopened.”

So How come a conversation remain in an snoozed state even after there is a comment from either admin or customer?

A comment part type is defined as: Standard reply from customer or admin to a conversation (defined at: https://developers.intercom.com/docs/references/1.4/rest-api/conversations/conversation-part-model#conversation-part-types) 

These are the part-types appearing with snoozed state

1    comment
2    conversation_attribute_updated_by_admin
3    conversation_sla_paused
4    merged_primary_conversation
5    operator_workflow_event
6    note
7    participant_added
8    participant_removed
9    ticket_state_updated_by_admin
10    conversation_sla_unpaused
11    priority_changed
12    entity_linked
13    forwarded
14    conversation_sla_target_missed
15    title_changed
16    merged_secondary_conversation
17    conversation_tags_updated
18    conversation_sla_applied_by_rule