My Jobs is a feature in OSC that lets you create and schedule background Python jobs that run on a cron schedule. Instead of managing your own infrastructure, OSC provisions an ephemeral job runner for each execution and cleans it up automatically when the job completes.

• Create scheduled background jobs from a Git repository (including private OSC Gitea repos)
• Set any cron expression as the schedule
• Trigger a job immediately with a single API call
• Suspend a job without deleting it, and resume it later
• Bind a parameter store to a job so its contents are injected as environment variables at runtime

• An OSC account on a paid plan (Personal, Professional, or Business)
• A Personal Access Token (PAT) for authentication — create one at app.osaas.io/dashboard/tokens
• A Python job in a Git repository (public or OSC Gitea)

My Jobs is accessible from the top-level Jobs tab in the My Apps section:

1. Navigate to My Apps in the OSC dashboard
2. Click the Jobs tab (alongside the Apps tab)
3. All scheduled jobs across your workspace are listed here, regardless of which app they belong to
4. Click Create job to add a new scheduled job. The create form includes a Parameter store selector (optional) — choose an existing parameter store instance to inject its values as environment variables when the job runs. Use the action buttons to run, suspend, or delete an existing job.
5. To modify an existing job, click the pencil icon next to it. The edit modal lets you update the cron schedule, source URL, worker command, and parameter store binding without deleting and recreating the job.

When a scheduled job is due, deploy-manager spins up an ephemeral eyevinn-python-job-runner instance, passes your source URL and worker command, and tears it down after execution. Credentials for private OSC Gitea repositories are resolved at trigger time — they are never stored in the job definition.

All endpoints require a PAT passed as Authorization: Bearer <pat> in the x-pat-jwt header.

Base URL: https://deploy.svc.prod.osaas.io

curl -s -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs

curl -s -X POST \
  -H "x-pat-jwt: Bearer $PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "dailysync",
    "cronSchedule": "0 9 * * 1-5",
    "sourceUrl": "https://github.com/myorg/myrepo",
    "workerCmd": "python jobs/sync.py",
    "configService": "my-param-store"
  }' \
  https://deploy.svc.prod.osaas.io/myjobs

curl -s -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync

curl -s -X PATCH \
  -H "x-pat-jwt: Bearer $PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "cronSchedule": "0 8 * * 1-5",
    "sourceUrl": "https://github.com/myorg/new-repo",
    "workerCmd": "python jobs/new_entry.py",
    "configService": "my-param-store",
    "configApiKey": "new-key"
  }' \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync

Only the fields you include in the body are changed. Send "configService": null or "configApiKey": null to clear those fields. Omit a field entirely to leave it unchanged.

curl -s -X POST \
  -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync/run

The response is returned immediately (HTTP 201) once the job runner is started. OSC polls the runner in the background and updates lastRunStatus to success or failed once the job completes — the same behavior as a scheduled run. Poll GET /myjobs/dailysync to check the outcome.

curl -s -X POST \
  -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync/suspend

curl -s -X POST \
  -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync/resume

curl -s -X DELETE \
  -H "x-pat-jwt: Bearer $PAT" \
  https://deploy.svc.prod.osaas.io/myjobs/dailysync

• Python Job Runner service
• Personal Access Tokens