EC2 instance cleanup job fails to remove some stale nodes

[achantavy]

Description:

What issue is being seen? Describe what should be happening instead of the bug, for example: Cartography should not crash, the expected value isn't returned, the data schema is wrong, etc.

Observed behavior: we are noticing each sync run leaving behind some small number of nodes each time.

match(i:EC2Instance) where not (i)--(:AWSAccount) return distinct i.lastupdated, count(distinct i) order by i.lastupdated desc;

returns

Expected behavior: cleanup jobs should remove all nodes and relationships where the update tag on the current resource type is not equal to the current update tag. There should be 0 rows returned from the above query because EC2 instances should always be associated with an AWS account.

To Reproduce:

Steps to reproduce the behavior. Provide all data and inputs required to reproduce the issue.

Not sure. Maybe running this on a large enough graph.

Logs:

If applicable, copy and paste your console log with the failing stack trace.

Not sure.

Please complete the following information::

• Cartography release version or commit hash [e.g. 0.12.0 or 95e8e11]
  0.94.0