We allow our users to deploy a new NFT contract to create their own personal collection of NFTs. We want to use the Sentinel to monitor the paid mint events so we can confirm these occurred before updating the values in our database.
We've been able to set this up already, however, is there a maximum number of contracts one Sentinel can monitor? The contracts all have the same ABI and conditions for monitoring are the exact same between them. We are just updating the sentinel and adding a new contract to it upon deployment.
However, I've noticed in the logs that it's returning a concerning message when we make the updates:
"Sentinel was triggered", followed by "Condition matches not found for Sentinel".
The sentinel still updates with the new contract though, so I'm not sure if this is something to worry about or not?
Environment
The Sentinel which triggers an autotask.
Details
No major issues. Just a couple questions for clarification:
Is there a maximum number of contracts one Sentinel can monitor?
Are the following messages from the Sentinel something to be concerned about or can they be safely ignored? Sentinel updates seem to take place despite these messages:
"Sentinel was triggered", followed by "Condition matches not found for Sentinel".