Skip to content

5. Review and publish

The final step lets you review the whole observation in one place and publish it. Once published, the observation is visible to the scheduler and starts competing for telescope time.


This step shows a Pre-publish checklist. All four must be green before the Publish button enables:

  1. At least one observing grant selected (step 1).
  2. Target has a name and position (step 2).
  3. At least one data request (step 3).
  4. Observation has a name (step 4 — Identity section).

A red item means that step needs attention; jump back to it from the stepper at the top of the editor. Publish appears both in the header and in place of the Next button at the bottom.

Below the checklist, a read-only Summary card lists the owner, observation name, number of epochs, observing grants and requests, the target, and any project you chose, and an Observation spec card shows the exact spec that will be submitted as JSON, with a Copy button.


When you click Publish, the server validates the spec (each request and configuration, and the scheduling settings) and checks that every selected observing grant is active, belongs to the owner, and is one you hold. It then creates the observation, creates or attaches the project you chose on the Configuration step, and takes you to the new observation’s page. If a check fails, a Publish failed banner says why, and you can fix it and try again.

Publishing does not check quotas or whether any telescope can actually run the requests; use the instrument bar’s compatibility count before you publish, and see Credits and quotas below.


You don’t have to do anything to keep your work: a new observation is kept in this browser until you publish it, and the hub offers Resume in-progress observation when you come back. To keep a copy you can return to from any browser, use the Save as draft button on this step. It saves your in-progress observation spec under the observation’s name, and you can reopen it later from Saved specs on the hub (or delete it there). Saving a draft does not create an observation — nothing is scheduled or charged, and it won’t show up in your observation list.


Once the observation exists:

  • Editing remains open. Skynet does not freeze an observation once it’s published. Edit on the observation’s page reopens these same five steps on the live observation; change fields, swap requests, change the target, or update scheduling parameters, then click Save changes on this step. Editing costs nothing extra; see “Credits and quotas” below.
  • The scheduler starts evaluating it. Within a scheduler cycle (typically minutes), tasks start to appear on the observation’s page.
  • You can watch it run. Head to the observation detail page — see Observation detail.

A common surprise worth calling out:

  • Publishing an observation costs nothing. You can create as many observations as you want without spending any credit.
  • Credits are charged as tasks complete. Each task that finishes on a telescope records a charge against the observing grant that funded it; the observation’s eventual cost is the sum of its completed tasks.
  • Throttling is quota-driven. Accounts and grants don’t carry a single “limit” — each can have zero or more quotas attached, defining caps like “max 500 credits per week” or “max 10 000 credits total.” All active quotas must be satisfied; the scheduler stops placing new tasks as soon as any one of them would be exceeded.
  • Quota-exceeded observations stall, they don’t error. When a quota fills up the scheduler stops placing new tasks; existing tasks continue, and scheduling resumes once the relevant quota period rolls over or new credits become available.

If you’ve created several observations and one of them isn’t making progress, check the quotas on your account and grants before assuming a scheduling bug — quota state is by far the most common cause.


If you publish an observation and decide you don’t need it, Cancel it from its page. The web app has no delete button; the API can delete an observation only until it has generated tasks, and only for someone allowed to manage its roles (normally the owner). After that it carries execution history and can only be canceled.


← 4. Configuration · Follow an observation →