Environments Beta AWS SM sync not configurable

Hi community.

Any one else noticed that 1Password Environments (Beta) had a recent problem with the destination sync to AWS Secrets Manager? 

In the last 24 hours, we noticed that

1. all our environments no longer have a AWS Secrets Manager "Destination" config
2. secret changes in the desktop app are no longer synced to the previously configured AWS Secrets Manager destination (add/delete/update a secret for a specific environment)
3. when configuring a new AWS Secrets Manager destination (either an existing environment or a new environment), pressing "Create integration" appears to work, however the config is not saved.  See point 1 above.

It was working fine yesterday (around 5pm GMT+10 6th May 2026) but we noticed the above issues this morning (around 10am GMT+10 7th May 2026)

So its clear, the OSX desktop app still 

• lists the available environments
• the desktop app UI allows us to added/delete/update a secret & the values are persist within 1password
• op command line can list the secrets including the recently edited secret key/value

We're using

• OSX 26.4.1
• 1Password Desktop for Mac 8.12.12 (81212044) Production channel
• Also tried the Nightly 1Password Desktop for Mac 8.12.20 (81220001) but it has the same symptoms

1P_Phil​ ​we have 23 1Password environments of which 14 had a working AWS Secrets Manager destination configured.  Its been working great the past few weeks & we love the product.  Maybe we've tripped on a bug. Sharing the above details to help make the product better.  Thanks