Administration Area

BETA

Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.

The Administration Area provides read-only access to Jobs and execution history. Inspect schedules and custom configuration, find failed runs, and read execution messages. Running Jobs and changing their configuration are outside this Area's scope.

Get Started covers connection and access setup. REST paths below are relative to the Dataset base URL.

Available Capabilities

Capability	REST Endpoint	MCP Tool
List Jobs	GET /administration/jobs	list_jobs
Get a Job	GET /administration/jobs/{jobId}	get_job
List executions	GET /administration/jobs/logs	list_job_logs
Get an execution	GET /administration/jobs/{jobId}/logs/{logId}	get_job_log

Jobs and Details

List Jobs to review their schedules, enabled states, and latest execution summaries. Use a returned Job ID to retrieve custom configuration and other details. Job IDs are GUIDs. Schedules use UTC cron expressions; a Job without a cron expression has no periodic schedule. Its enabled state controls scheduling and enqueueing, rather than indicating whether it is currently running.

Execution History

List executions across the Dataset or for one Job. Choose a date range using fromDate and toDate; it includes executions started during the full UTC day of both dates. Optionally filter by outcome to find completed runs, runs with warnings, or failures.

Cursor Pagination

REST and MCP return executions newest first and support cursor pagination. Start without a cursor, then pass nextCursor as beforeLogId for older runs or previousCursor as afterLogId for newer runs. Supply only one cursor per request and keep the Dataset, filters, dates, and page size unchanged. A null cursor means there is no further page in that direction.

For example, use list_job_logs for a date range with result: "faulted" to find failures. Continue with the same arguments and beforeLogId set to the returned nextCursor until it is null.

Execution Details and Results

Use the execution's jobId and id as jobId and logId to retrieve its details and chronological log messages. Log IDs are positive integers, and the execution must belong to the selected Job and Dataset. The log details visible to you depend on your access.

An execution's result can indicate completion, completion with warnings, or failure. A null result means no outcome is available; it does not establish success or failure. Finish time and duration may be unavailable for unfinished runs.

REST returns 404 Not Found for a missing Job or execution. MCP returns {"job": null} or {"log": null}, respectively.

For complete inputs and response schemas, use the API reference or MCP tool discovery.