Scheduled automation to create tickets from assets, but not create duplicates

[Sara Rowe]

We're using assets to track recurring/annual payments. When the renewal date (asset attribute) is within 90 days, I want to create a ticket in our project. Currently, the date range is set for anything in the next 90 days in the AQL. 

What works: 

Scheduled Trigger - Branch on AQL - Create Issue

The Problem: 

Creating duplicate tickets. I only need one reminder for each payment. 

What I've Tried: 

Various versions of the AQL search (branch and look-up objects), then lookup work issues, then compare lookup size. But the scope is not right/too big and I'm getting an "unable to run the search while custom values were being defined" error. Error and current testing iteration (with manual trigger) in screenshots. I get the same error if I schedule the automation or manual trigger. 

The AQL search: objectTypeId = 932 AND "Status" != "Closed" AND "Next Payment Date" > now() AND "Next Payment Date" < now(90d)

[Mikael Sandberg]

I would change the AQL to only search on objects that are 90 days out when the automation is run, that should prevent any duplications. Something like this:

objectTypeId = 932 AND "Status" != "Closed" AND "Next Payment Date" = now(90d)