Run and inspect results

Run a request and read the status and result of each operation.

The app and dynomate-cli requests run use the same runtime. For the order, error, and status rules, see Dependencies and execution.

Run a Request

1. Open the request.
2. In the title bar, select the Global and Collection environments. See Configure environments.
3. Select Run, or press Cmd/Ctrl+Enter.

You do not have to save first. Dependencies run before the operations that need them.

When the button shows Checking…, Dynomate validates the full request. If it finds a problem, it makes no AWS calls. See Validation and Problems before a run.

Confirmation

Dynomate asks you to confirm one time before it runs a request that:

• Deletes or truncates a table.
• Uses an endpoint URL from the request file, not from a saved AWS profile.

The Confirm request dialog lists the Table changes, with guard values, and the Request-defined endpoints. A target that depends on an earlier result shows Resolved during run.

Select Confirm and run to start, or Cancel to stop. If you change the draft, environments, or profile settings before you confirm, Dynomate discards the run.

Item writes, endpoints from a saved profile, and changes of profile or region do not need confirmation. See Safety.

While It Runs

Each row in the results panel shows Running, Processed, or Waiting. A status line shows the current operation, the elapsed time, the completed count, and the endpoint.

The final statuses show when the run ends. Until then, you cannot save or run.

Cancel a Run

Select Cancel in the request header. Dynomate stops the run and shows which operations completed.

Results Panel

The panel header shows the request status, the duration, and the number of operations that ran, that Dynomate skipped, and that are destructive.

Each row shows the operation name, type, status, duration, and a summary, for example 1 item returned. A Destructive badge marks destructive operations. Select a row to expand it. It has three tabs:

• Data: the result, as a table for items and rows. For a skipped operation, it shows the reason.
• Metadata: counts, pagination keys, consumed capacity, AWS request IDs, endpoints, warnings, and error details.
• Raw: all data as read-only JSON, with exact typed values.

Resize, collapse, and reopen

• To resize the panel, drag its top edge, or focus the edge and use the arrow keys, Home, and End.
• Collapse results shows only the header. Select the header to expand the panel.
• To open a closed panel, select Request actions, then Open results panel.

Statuses

Each operation has one of these statuses:

• Success: the operation completed.
• Failed: the operation returned an error. Metadata shows the details.
• Skipped: the operation did not run. Data shows the reason.

The request has one of these statuses:

• Success: all operations succeeded, or Dynomate skipped only disabled operations.
• Partial: one or more operations failed, or Dynomate skipped them for a different reason.
• Failed: validation failed, you canceled, the request timed out, or an operation failed with Stop request.

See Outcomes and Error policy.

Results From an Earlier Draft

The panel keeps only the last run. If you change the request or its environments, the panel shows These results belong to an earlier draft. Run again to update the results.

Effective Endpoints

If a request uses a custom endpoint, for example DynamoDB Local, Effective endpoints lists it before the run and in the results panel.

Each entry shows the operation, the service, the profile, the region, and the source. The source is Request-defined or Saved profile. See Endpoints.

Problems Before a Run

If a check fails before the run, the results panel shows each diagnostic with its operation, message, code, and line. Select a diagnostic to go to the field.

If a field is not valid, the panel shows Resolve the input errors before running. Dynomate focuses the first field that is not valid. See Error codes.