Expiry date field for membership category

This is currently working as intended, @harish_ravikumar. We technically don't have an expiry date field under the hood. We have mm/yyyy fields and dd/mm/yyyy fields, both of which are simple "date" fields because they could be used to store a litany of info. Issue date, expiry date, birthday, date of purchase ... and that's just off the top of my head. The expiry dates are, of course, relevant to Watchtower. It cares about these so it can let you know when something is expiring. But, not every date field is intended to contain an expiry date and since there is no expiry date specific field, Watchtower has no way to know whether date fields you add are intended to be that or not.

So, how does 1Password tell which of these fields are relevant and which aren't? In short, it often doesn't know, but for items we know need an expiry date, we designate fields in the default template as expiry dates. These are special and only exist as part of the templates. Watchtower monitors these fields and these fields only to warn you when something is expiring while avoiding telling you that you are expiring soon if your birthday is coming up. As soon as you change the field's type, though, it becomes a custom field instead and Watchtower will ignore it because it no longer knows whether or not this is, genuinely, still an expiration date field. Once you've made that sort of change, the only way to get Watchtower to start monitoring that field again is to restore the item from item history to a time before you altered that field in any way.

On behalf of bundtkate, you are welcome @harish_ravikumar!

If you have any other questions, please feel free to reach out anytime.

Have a wonderful day :)