Why the first check can be slow

If you run a check after Periscope has been idle for a while, the first one takes longer than the rest. This is expected, and it isn't a fault.

To save energy, the model that reads your documents rests when it hasn't been used for a stretch of time. The first check after that quiet period wakes it up, which adds about twenty seconds. Every check after that, while the model stays warm, runs at normal speed.

There's nothing to do differently. Submit the check as usual and let it run. If it seems to sit for a moment longer than you expect, that's the wake-up, not a stall.

It's also worth knowing that Periscope is a proof of concept running on test hardware, not the production setup a live version would use. Checks here are slower across the board than they'd be once Periscope is fully deployed.

If a check takes far longer than twenty seconds or doesn't complete at all, that's separate from this normal wake-up delay. Give it a moment and try again.