Zorki needs to end its Selenium session after it finishes an Instagram scrape, but because it's usually still forwarding requests when it finishes a scrape, it can't do so without raising Selenium errors.
To get around that, we need to ensure that Zorki ends its request forwarding earlier, waits for its queued requests to finish forwarding before it ends its Selenium session, or doesn't break when a session is quit while requests are still being forwarded.
We could tell Zorki to sleep for n
seconds before ending its Selenium session in the hopes that by then, all requests would be forwarded. But explicit sleeps aren't very nice, and there's always a chance that if we try to minimize the sleep duration, we'll run into an instance in which Selenium fails to forward requests before Zorki ends the Session (our problem right now).