Email address PATCH via SKY API not reflected in RENXT UI (primary, active email)

Question

Hi BB community,

I’m seeing an issue where an email address update made via the SKY API is successfully persisted at the email address resource level, but is not reflected in the Raiser's Edge NXT UI for the same constituent. I’d like to confirm whether this is expected behaviour (e.g. latency / eventual consistency) or something that needs investigation.What I’m doing

* I am updating an existing email address using
PATCH /constituent/v1/emailaddresses/{email_address_id}
* The PATCH:* updates the primary email
* email is active
* do_not_email = false

* The PATCH request returns success (200), and:* GET /constituent/v1/emailaddresses/{email_address_id} shows the updated value
* GET /constituent/v1/constituents/{constituent_id}/emailaddresses also shows the updated value

What I’m seeing

* In the RENXT UI (Web View), the constituent record is still displaying the previous email address
* The UI does not reflect the updated primary email after the PATCH
* I have confirmed I’m looking at the correct constituent and email record
* There is only one primary email on the record

What I’ve already checked

* The email is marked primary and active
* The constituent is not marked “Requests no email”
* The email itself is not marked “Do not email”
* No secondary primary email exists
* The update persists when re‑querying the API

Questions

* Is there a known delay or eventual‑consistency behaviour between the Email Address endpoint and the RENXT UI (e.g. Read Optimized Data Store latency)?
* Are there additional internal flags or rules the UI uses to determine which email is displayed that are not exposed via the Email Address API?
* Is there any additional action required to trigger the UI to reflect an email address update made via the API?

Thanks in advance.

Kind regards,

Kat

Kat Yang · Answer

https://community.blackbaud.com/discussion/comment/313251#Comment_313251

Hi Carol,

Thank you so much for your reply. I’ve since discovered that the constituent I was testing has a spouse record with the same email address. It looks like the API PATCH updated the spouse’s email record instead, which is why I’m seeing the change reflected in the UI there.

Both records share the same email value but have different email_address_ids, and only one of them was updated by my script. I’ll update my logic to account for this.

Thanks again for your help!

Cheers,

Kat

Carol Grant · Answer

Hi @Kat Yang - I only have a few troubleshooting steps you can try.  It appears you are doing everything correctly.  No other fields are required except the email_address_id which you have.  You may have to refresh the NXT page a few times for it to appear but I don't think there is any long latency.

Have you done the Try it in the API reference under Constituent- PATCH Email Address (Edit).  Does it work there when you put the email address id in?

Lastly, many times we think we are in the production environment in Power Automate but some people have a TEST mode.  Make sure you are in Production in Power Automate or that you aren't in a different database altogether in Power Automate.

-Carol Grant