mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation allows users to list executions of a specific Cronjob from the mittwald mStudio API. It is useful for monitoring and auditing scheduled tasks by retrieving detailed execution records, including filtering by status, date range, and sorting order. Practical applications include tracking job success rates, debugging failed runs, or analyzing execution performance over time.

Properties

Name Meaning
Cronjob Id The unique identifier of the Cronjob whose executions you want to list (required).
Limit Maximum number of execution records to return in one response.
Skip Number of execution records to skip before starting to collect the result set.
Page Page number for paginated results.
Since Start date/time filter to list executions occurring after this timestamp.
Until End date/time filter to list executions occurring before this timestamp.
Status Filter executions by their status. Options: Complete (default), others may be supported.
Triggered By User Boolean flag to filter executions triggered manually by a user (true/false).
Sort Order Order in which to sort the returned executions. Options: Oldest First, Newest First, Slowest First, Fastest First.

Output

The node outputs a JSON array containing the list of Cronjob execution objects retrieved from the API. Each object typically includes details such as execution ID, start and end times, status, duration, and trigger source. This structured data can be used downstream for reporting, alerting, or further automation steps.

If binary data were involved (e.g., logs or artifacts), it would be summarized here, but this operation focuses on JSON metadata about executions.

Dependencies

  • Requires an API key credential for authenticating with the mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de and expects JSON responses.
  • No additional external dependencies are indicated beyond the API access.

Troubleshooting

  • Invalid or missing Cronjob Id: Ensure the Cronjob Id property is correctly set; otherwise, the API will not return any executions.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Empty results: Check filters like date range (Since, Until) and status to ensure they match existing executions.
  • Pagination issues: If using Limit, Skip, or Page, confirm values are within acceptable ranges to avoid unexpected empty pages.
  • Sorting confusion: Understand the meaning of sort options to get expected ordering; e.g., "Slowest First" sorts by execution duration descending.

Links and References

Discussion