Why does the Snyk Security in Jira App stop importing vulnerabilities after a while?

[Malcolm Vidal]

I am testing the Snyk Security in Jira application in our Jira sandbox. 

The first few containers imported correctly, they show up in the "Security Containers" section, and their respective vulnerabilities populate the "Vulnerabilities" section.

After a while, whenever I wanted to import a new container, the vulnerabilities stopped showing up. Also, I have removed one of the containers that worked, and tried to re-import it - but this time the vulnerabilities did not show up.

1. Is this logged anywhere? (I would like to see the errors)

2. Is there some limit to how much data can be imported on the sandbox? 

3. Could this be an issue on Snyk's end as the application is still in Beta? 

Update:

I continued testing by switching Project in Jira, once again the first 5 imports worked and the vulnerability section was populated.

After that, same issue for the rest, not populating the vulnerabilities. Is there some limit to the amount of containers we can import per Jira project?

[Jim Nofsinger]

I have run into the same issue when importing more than 7 items anything new stops showing up. 

I have 14 pages of vulnerabilities (most which are low or "no fix available" from Snyk).  If I ignore this or try to reduce the amount of vulns it doesn't make other projects show up... so I think it is related to the number and not count like suggested with the original comment.

Right now I have written automation rules and can generally use the integration (although it is still lacking significant support for auto-closing tickets).  Limiting it to a 5-7 project items isn't useful to us or any larger company.