Author Tools

The Author Tools section of the pd4castr UI lets you monitor your model runs, check their statuses, and debug failures.

Accessing the Author Tools

Navigate to the /publisher path in the pd4castr UI.

Note that to view the Author Tools, your organisation must have model authoring access. contact us to get set up.

Viewing Model Runs

Select a model from the left sidebar to view its run history in the main panel.

The main panel shows a live-updating list of model runs for the selected model. The list refreshes automatically, so you don’t need to manually reload the page to see new runs.

Runs are displayed 25 at a time. Click Load More at the bottom to fetch older runs.

Model Runs

Each model run appears as a row in the list, showing:

• Status badge — a colour-coded label indicating the current state of the run:

  Status	Colour
  Pending	Grey
  Input Files Prepared	Purple
  Running	Blue
  Completed	Green
  Failed	Red

• Created timestamp — when the run was queued.

• Run ID — a unique identifier displayed in monospace text.

Click the expand arrow on the right side of a card to reveal the full run details.

Model Run Details

The expanded view shows additional information about the run:

• Created At — when the run was queued.
• Run Datetime — the temporal context of the forecast (the date and time the forecast is “for”).
• Started At — when the model container began executing.
• Completed At — when output processing finished.
• Errored At — when the run failed, if applicable.
• Sensitivity — which sensitivity scenario this run belongs to, or empty for base runs.
• Container ID — the container ID. You may need this for support requests.
• Error — for failed runs, the error message.

Common Workflows

Verify a Newly Published Model

After publishing a model for the first time, open the Author Tools and select your model from the sidebar. Check that the first run has moved through the status stages and reached Completed.

Debug a Failed Run

If a run shows a Failed badge, expand the card to read the error message. The error text and container ID can help you identify whether the failure was caused by your model code, an invalid SQL, or a platform issue.

Monitor Automatic Run Cadence

For models using the automatic run mode, use the run history to verify that runs are triggering as expected. Check that new runs appear at the expected frequency and that sensitivity runs complete alongside base runs.

Next Steps

To learn how models get published, see Publishing. For details on how automatic runs are triggered, see Run Modes & Scheduling.