Came from discussion in issue #19. If a user queries for a term, then queries for it again, it will launch two parallel jobs querying for the same token. Instead, the API should first check if there's an existing job that's querying for the given token and, if so, wait for that job rather than launching a new one.
Came from discussion in issue #19. If a user queries for a term, then queries for it again, it will launch two parallel jobs querying for the same token. Instead, the API should first check if there's an existing job that's querying for the given token and, if so, wait for that job rather than launching a new one.