It was posted before your campaign started. Lancer doesn't go back over old jobs — it only processes jobs posted after you start a campaign.

Your filters excluded it. Keywords, budget, region, experience level or other filters may have ruled it out. Open the campaign's Jobs tab and check.

The Categories filter caught it. Upwork's own category tagging is unreliable, so a relevant job can be miscategorized and filtered out. We usually recommend removing the Categories filter and targeting with keywords instead.

It's a private or invite-only listing. Those can't be applied to through normal bidding.

The AI judged it unsuitable. Your Knowledge Base decides fit. If it got this one wrong, you can still bid manually (see "Manually apply to a job Lancer skipped") and tighten your Knowledge Base so similar jobs are judged correctly next time.

It needs an extra step or is closed — e.g. an Upwork "AI interview" / extra questions, or the job is no longer available.

Another campaign sharing the same Upwork bidding identity already handled it. Lancer prevents duplicate proposals at two levels:
​
​Same bidding entity — two campaigns that submit under the same agency on the same connected account always conflict, regardless of which contractor is assigned to each campaign. Upwork only permits one proposal per agency per job, so only the highest-priority campaign whose AI rated the job suitable wins; the others are automatically archived.
​
​Same person — a freelancer-mode campaign and an agency-mode campaign that resolve to the same person (same profile name or same contractor name) also conflict, even across modes.
​
​Different entity and different person on the same account — for example, two distinct agencies connected under the same account, or your own freelancer profile vs a different agency where the person name doesn't match — these do not block each other.
​
A campaign that rated the job unsuitable does not block suitable campaigns from bidding.