Skip to main content

Repeated uploads of CP-IS records relating to 17-year-olds and unborn children

In this article, we explain why CP-IS records for 17-year-olds and unborn children may be repeatedly uploaded.

Y
Written by Yusef Abulaynain
Updated over 5 months ago

In version 22.2.0.0, we introduced functionality to prevent records for young people over 18 from being sent to CP-IS. However, the system was calculating age based only on the year of birth—not the full date. As a result, once a child entered the year of their 18th birthday, they were removed from the upload, even if they hadn’t actually turned 18 yet.

Mosaic then used separate code to identify that they were still relevant for CP-IS, added them back to the table, and uploaded them again causing repeated uploads.

We're also investigating whether this age calculation issue is behind a separate problem, where CP-IS responses are received but an error says the child record can’t be found in Mosaic. We’ll update this article once we confirm the cause.

We’re pleased to let you know that patches for the repeated upload bug have now been released. These patches are:

  • 22.2.3.4

  • 22.2.4.3

  • 22.2.5.1 (only for customers already on 22.2.5.1—mainly ACG early adopters)

The patch is an EAR file only, but please make sure you check any patch or minor release requirements between your current version and the patch you’re applying.

Let us know if you need help reviewing compatibility or applying the patch.

Did this answer your question?