Jobs Retries And Resolution

Jobs Retries And Resolution

Purpose: operate async jobs explicitly and handle failure states deterministically.

UI Flow

1. UI shows queue and task status per account.
2. User opens job detail when failed or stuck.
3. UI allows Trigger, Retry, and Resolve.
4. UI highlights last_error_code and last_error_detail.
5. UI refreshes task status after job action.

Client Library Flow

const jobs = await api.jobs.list(accountId, { limit: 50 });
const failed = jobs.data.filter((row) => row.failed_at);
for (const job of failed) {
  await api.jobs.retry(job.id);
}
const inFlight = await api.jobs.list(accountId, {
  q: "imap_sync_messages",
  limit: 20,
});

HTTP/curl Flow

API_BASE_URL="https://api.inbox-manager.com"

curl -sS "${API_BASE_URL}/api/accounts/${ACCOUNT_ID}/jobs?limit=20&offset=0" \
  -H "authorization: Bearer ${BEARER_TOKEN}"

curl -sS -X POST "${API_BASE_URL}/api/jobs/${JOB_ID}/trigger" \
  -H "authorization: Bearer ${BEARER_TOKEN}" \
  -H "content-type: application/json" \
  --data '{}'

curl -sS -X POST "${API_BASE_URL}/api/jobs/${JOB_ID}/retry" \
  -H "authorization: Bearer ${BEARER_TOKEN}" \
  -H "content-type: application/json" \
  --data '{}'

curl -sS -X POST "${API_BASE_URL}/api/jobs/${JOB_ID}/resolve" \
  -H "authorization: Bearer ${BEARER_TOKEN}" \
  -H "content-type: application/json" \
  --data '{"note":"handled after provider maintenance window"}'

Error Taxonomy Direction

• Worker now records categorized last_error_code values for:
  • transient connectivity
  • authentication
  • authorization
  • configuration
  • payload validation
  • not found