Can AWS DMS detect new PostgreSQL table partitions without restart?

I have implemented a AWS DMS task to replicate RDS PostgreSQL (source) changes to Kinesis Data Streams (target). At the moment, the task is responsible for only replicating a single table, which is a partitioned table in PostgreSQL. These are the task mapping rules:

{
    "rules": [
        {
            "mapping-parameters": {
                "partition-key-type": "primary-key"
            },
            "object-locator": {
                "schema-name": "public",
                "table-name": "sales_p_%"
            },
            "rule-action": "include",
            "rule-id": "1",
            "rule-name": "1",
            "rule-type": "selection"
        }
    ]
}

We have triggers to create new sales partitions in our application. However, when a new partition is created for this table, DMS doesn't automatically detect it and start the CDC replication. The new partition is not listed in the "Table statistics" tab for the task, and inserts/updates for the new partition are not sent to Kinesis.

As soon as the DMS task is stopped and then resumed, the new partitioned table is discovered, and ongoing replication starts working.

Is AWS DMS capable of discovering new tables matching an include table name, without needing to create an automated process that stops/resumes the task as a workaround?