Skip to main content
For the complete documentation index, see llms.txt.
An Ephemeris Push task automatically generates a fresh orbit ephemeris (OEM) for each of your spacecraft and uploads it to one or more external space catalogs on a schedule — so you never have to export and upload ephemeris files by hand. Route: /tasks

​
Overview

Operators with a standing obligation to keep external catalogs supplied with current ephemeris — for example Space-Track or the EU Space Surveillance & Tracking (EU-SST) network — can configure one Ephemeris Push task and leave it running. On every scheduled run, Valar:
  1. Generates a current CCSDS Orbit Ephemeris Message (OEM) for each configured spacecraft, and
  2. Uploads it to each configured catalog.
Each upload is tracked as an individual delivery leg (one per spacecraft-and-catalog pair), so you can see exactly what was delivered, what was skipped, and why. Use an Ephemeris Push task when you need external catalogs to stay current automatically, without manual exports or uploads.

​
Prerequisites

Before a spacecraft will be delivered on a run, it must meet a few conditions. Spacecraft that don’t yet qualify are skipped (not failed) — the task keeps delivering for every other eligible spacecraft, and skipped spacecraft resume automatically once they qualify.
  • A NORAD ID. The spacecraft must have a NORAD catalog ID configured on its Spacecraft page. Without one it is skipped with NO_NORAD_ID.
  • Current orbit data. The spacecraft’s orbit must be fresh enough to publish. Stale or degraded orbits are skipped (ORBIT_STALE / ORBIT_DEGRADED) until newer orbit data is available.
Space-Track and EU-SST credentials are configured centrally by your administrator — you do not enter any catalog credentials when creating a task.

​
Setting up a task

1

Open the Tasks page

Go to Tasks (/tasks) and select Create Task.
2

Choose the Ephemeris Push type

In the task-type picker, select Ephemeris Push.
3

Select spacecraft

Choose one or more spacecraft to push ephemeris for. A spacecraft with no NORAD ID shows a No NORAD ID warning — you can still include it, but it will be skipped on each run until a NORAD ID is assigned.
4

Choose catalogs

Select one or more delivery targets: Space-Track and/or EU-SST.
5

Set the delivery cadence

Enter a schedule interval using the shorthand grammar (6h, 12h, 1d, 1w). The minimum is 6 hours; the default is daily (1d). An interval below 6 hours is rejected with the inline error “Schedule interval must be at least 6 hours.”
6

Review and create

Review your spacecraft, catalogs, and cadence, then create the task. It begins running on the schedule you set.
The task’s overall run is reported as succeeded even when some spacecraft are skipped — a run only fails on a systemic fault (for example, a catalog is unreachable). Per-spacecraft skips never fail the run.

​
Reading delivery-leg outcomes

Open the delivery-legs view for any Ephemeris Push run to see one row per delivery leg. Legs are ordered by severity — failed first, then skipped, then delivered. Each leg carries a colour-coded outcome badge:

​
Scheduling notes

  • The minimum delivery cadence is 6 hours; the default is daily (1d).
  • The task runs unattended on its schedule. A manual run is available from the task itself.
  • Skips are self-healing: a spacecraft skipped for a missing NORAD ID or a stale orbit resumes delivery on the first run after the underlying condition is resolved — no manual re-trigger needed.