In this section · 4 articles

Paper Queue never reads a page, or reading fails

A page in Paper Queue stays Created, Processing or Re-Queued, or ends as Skipped (no AI) or Failed. Find out what each status means and how to get the page read.

Applies to
Question Bank 3.5 and later
Who can do this
Platform owner, Administrator, Team member
Permission
feature.qb.paper_queue.requeue
Where
Question Bank › Paper Queue
On this page

Symptom

You added a page to Question Bank › Paper Queue, and no questions come out of it. No message appears. Check the page's Status:

StatusGo to
Created for a long time1
Processing for a long time2
Re-Queued for a long time2
Skipped (no AI)3
Failed4

Check these, in order

1. Created: nobody started the reading

Saving a page doesn't start reading it. Question Bank doesn't schedule the reading either: waiting pages are read only when someone runs the reading command on the server.

Fix: Ask whoever runs your server to run it. It takes one waiting page per run unless given --limit:

Bash
php artisan paperqueue:process --limit=10

To read new pages without anyone remembering, they can add that command to the server's cron. To send one page for reading without the command, open its Review screen and select ReQueue the Paper. See Import questions from an exam paper.

2. Processing or Re-Queued: the reading waits in the queue

If your Laramin queues background work (Connection in Developer Tools › Developer Settings › Queue Settings is Database or Redis), the reading waits until a queue worker picks it up:

  • Pages started by the reading command go to a separate queue named process_paper_queue. A plain queue worker, and your Laramin's scheduled jobs, work through the main queue only. So these pages stay Processing.
  • Pages sent with ReQueue the Paper go to the main queue. So a re-queued page can be read while new pages stay Processing.

Fix: Ask whoever runs your server to keep a queue worker running that includes both queues:

Bash
php artisan queue:work --queue=default,process_paper_queue

If re-queued pages don't move either, nothing works through the main queue. See Scheduled jobs don't run.

Careful: The reading command also picks up pages that show Re-Queued. A page sent with ReQueue the Paper can be read a second time if the command runs while it's still waiting, and each reading is charged by your AI provider.

3. Skipped (no AI): no AI provider could read it

No usable AI provider or model was available, so nothing was tried and nothing was charged. An image page needs a model that can read images; HTML and JSON pages need one that generates text.

Fix: Set up a provider and model in AI Manager. See Connect an AI provider. Then select ReQueue the Paper on the page.

4. Failed: reading failed three times

The AI provider was tried three times and failed each time. The reason is only in your Laramin's log, on a line starting [questionbank] extraction failed for paper queue.

Fix: Check the provider's usage, limits and key. See AI requests fail or are skipped. Then select ReQueue the Paper.

Still not working?

Raise a ticket from Support Center in your Laramin app. Include this page's link, the page's title and status, and when it was added.