resume-campaign

Resume Campaign - Continue a Paused Campaign

Resumes a paused Campaign by replaying the apply loop on jobs that are still approved (or pending if approval was implicit). The user already approved the fit when the campaign was first launched, so no re-confirmation gate.

Live view: $JOBPILOT_WEB/campaigns/<campaign-id>.

Setup

Follow ../_shared/setup.md to load profile, resume, credentials - its health check aborts with the standard message if the backend is unreachable.

Phase 0: Resolve Campaign

Argument is <campaign-id>. If missing, list candidates and ask:

jobpilot-api GET /api/campaigns --query status=paused

Show each of .items as id, status, source, query.

Fetch the campaign + jobs:

CAMPAIGN_ID="<campaign-id>"
jobpilot-api GET "/api/campaigns/$CAMPAIGN_ID"
jobpilot-api GET "/api/campaigns/$CAMPAIGN_ID/jobs" --query page=1 --query limit=100

Verify status is paused. If completed or failed, stop: "Campaign is already . Nothing to resume." If in_progress, stop: "Campaign is still in progress. Stop the campaign from the UI first."

Refuse to resume if no job in .items is approved, pending, or applying: say "No resumable jobs (approved/pending/applying). If none were ever added, start fresh with the auto-apply skill." and stop.

Phase 1: Re-open the Campaign

Command status back to in_progress:

jobpilot-api POST "/api/campaigns/$CAMPAIGN_ID/status" --data '{"status":"in_progress","actor":"agent"}'

Keep the campaign's config.maxApplications as MAX_APPS (absent means no limit) for the stop condition below.

Phase 2: Replay Apply Loop

For each job where status === "approved", "pending", or "applying", score-descending - the same per-job flow as the apply skill's Apply Loop, delegated to the job-applier subagent one at a time:

1. Mark applying - PATCH the job to applying.
2. Apply - delegate to job-applier with its input from ../_shared/campaign-flow.md, brief omitted (the worker fetches it from the saved Job) and preSubmitReview: <true when MAX_APPS === 1, else false>.