When does File Match hold a file back?

The test of an automatic system is not what it sends. It is what it refuses to send. When File Match holds a file back nothing breaks: the job stays in your queue, like any other, and your tuner sees a card on it headed "The library did not send this one", with the reason.

Why would the work stop it?

The work does not match. The tuned file does not do exactly what was ordered. Either it does less, or it does more and you have not said that extra is fine. See how File Match decides.

Your library contradicts itself. The same bytes are recorded as doing two different things. The portal will not choose. Open the entry and correct it.

Why would the stored file stop it?

The tuned file is missing from storage. The record is there and the file is not. Replace it, or remove the entry.

The bytes have changed. The tuned file no longer matches the fingerprint taken when it was filed. Something altered it, so it is not sent and your administrators are alerted. Take this one seriously, and check where the file has been.

The format is not usable. The stored tuned file is in a format that does not suit this job.

It could not be stored on the job. The copy for this job failed to write. Check your storage space, then send it by hand.

Why would the customer's file stop it?

The read has not fully arrived. The job exists, but the file is still on its way. The portal tries again when it lands.

It is a full backup archive. Some tools can produce a full backup package rather than a read. That is not the same job, so a person looks at it.

Why would a locked file stop it?

It is a locked read of several regions. Bench and boot reads can hold more than one region, and those are done by hand.

It cannot be packed again for that tool. If a customer's read was locked, the tuned file has to go back in the same form. If the portal has no way to do that for this job, it stops. File Match and locked slave files goes through these.

Why would money stop it?

A dealer is over their limit. On a network, a job from a dealer draws on that dealer's balance. If it would pass the limit you set, the file is held.

The job is not paid. A job that still owes something waits until it is paid, then goes out.

What should I do when I see one?

Read the reason, then deal with the job as you would any other. A job held once is no problem. The same reason appearing again and again is a signal worth acting on.

• Many work mismatches usually means tuned files with loose or missing names. Name the work properly.
• Missing files usually mean an import that did not finish, or storage that moved.
• A changed file is never routine. Find out why before you trust that entry again.

You can have a message sent to your staff when something is refused. It is off to begin with, and the setting is on the AI Match page. Most shops start by reading the cards on the job, then switch it on once the reasons are rare.