Uploading large number of fingerprints fails #3535
Replies: 1 comment 4 replies
-
|
The only time I know someone encountered a failure to submit fingerprints was if they had one queued up, but then deleted the scene that used that fingerprint. Do you get any errors when clicking submit in the browser console (Ctrl+Shift+I)? |
Beta Was this translation helpful? Give feedback.
-
I had previously uploaded several batches, and testing the credentials works. |
Beta Was this translation helpful? Give feedback.
-
|
Wait... |
Beta Was this translation helpful? Give feedback.
-
|
Well, that seems to have cleared out the erroneous scenes, but the fingerprint count is the same and the upload still fails. |
Beta Was this translation helpful? Give feedback.
-
|
The clean task doesn't remove the fingerprints from the queue, so not surprised it didn't fix it. Not sure what's causing it. It might be exactly what you are suspecting that the queue is too long and it times out. The devs can probably help you with that. Fingerprints are stored in the browser's IndexedDB. You can delete the database attached to clear it, but it will remove the queue and tagger preferences. Ctrl+Shift+I > Application > IndexedDB > localforage |
Beta Was this translation helpful? Give feedback.
-
Just wondering if anyone else has gone through and matched like, I don't know, 900+ scenes and then realized that they had forgotten to upload the fingerprints?
I did that, and now the upload fails.
Anyone have any ideas about why or how to get them pushed?
Beta Was this translation helpful? Give feedback.
All reactions