data.retention_field_required

A field's retention: is on a field that can't be none, so its value could never be cleared.

Area 15, Personal data; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

A retention: on a field clears its value when its time is up and keeps the record. A field whose type doesn't end in ? must always hold a value, so there is nothing to clear it to. Here signup_ip is an IpAddress, which can't be none, so the address would be kept for ever, however long the retention says.

What it looks like

main.jadpo:

config {    signup_ip_retention: Duration {        default: 30d    }}entity Visitor {    id: Uuid    signup_ip: IpAddress {        retention: {            after: config.signup_ip_retention            since: created_at        }    }    created_at: Instant {        generated: Generated.on_create    }}

   |10 |         retention: {   |         ^^^^^^^^^ on a field that can't be `none`

(agent) at the end of the next: line means your coding agent can make the fix itself.

How to fix it

If the address should go and the visitor stay, make the field one that can be none:

entity Visitor {    ...    signup_ip: IpAddress? {        retention: {            after: config.signup_ip_retention            since: created_at        }    }    ...}

signup_ip is now none once the visitor signed up longer ago than signup_ip_retention, and code reading it handles a visitor without one. To delete the whole visitor instead, the retention: goes on the entity (On an entity).

Related

• Retention
• On a field
• Values that may be missing