GET /internal/schedulers

Returns the running status of all background schedulers in the current service

Responses

Status	Description	Schema
200	Query successful	dto.DataResponse-any
401	Unauthorized access	dto.Problem
500	Internal server error	dto.Problem

Referenced Schemas

dto.DataResponse-any

Field	Type	Required	Example	Constraints	Description
code	integer	No
data	object	No
message	string	No
timestamp	string	No

dto.FieldViolation

Field	Type	Required	Example	Constraints	Description
code	string	No			Code is the error code (optional). Used by programs to identify error types, such as "required", "format", "range".
description	string	No			Description is a human-readable error description. It should explain which rule was violated, such as "Must be a valid email address".
field	string	No			Field is the path to the error field. Use dot notation for nested fields, such as "user.email" or "addresses[0].city".
value	object	No			Value is the value that caused the error (optional, used in development mode). In production, this field may not be returned to avoid leaking sensitive information.

dto.Problem

Field	Type	Required	Example	Constraints	Description
code	integer	No			Code is a business error code. Used by programs to handle specific error scenarios. Example: 30101001
detail	string	No			Detail is a human-readable explanation specific to this error instance. It can contain specific error details, such as "Field 'email' is required".
errors	array of See dto.FieldViolation	No			Errors is a list of field-level validation errors (extended field). Following Web API standard practices, each error contains the field name and error message.
i18n_args	object	No			I18nArgs are internationalization parameters. Used to dynamically fill translation templates.
i18n_key	string	No			I18nKey is an internationalization key. Used for client-side localization of error messages. Example: "error.user_not_found"
instance	string	No			Instance is a URI reference to the specific occurrence of the problem. Usually the request URL, possibly including query parameters. Example: "/api/v1/users?limit=invalid"
request_id	string	No			RequestID is a unique request identifier. Used for log correlation and issue tracking. Example: "req_550e8400-e29b-41d4-a716-446655440000"
retry_after	integer	No			RetryAfter is used for 429 Too Many Requests responses. Indicates how many seconds the client should wait before retrying the request (RFC 6585).
service	string	No			Service is the service name. Used in microservice architectures to locate the source of the error. Example: "auth-service"
span_id	string	No			SpanID is the current span identifier. Used to precisely locate the current node in a distributed trace.
status	integer	No			Status is the HTTP status code generated. Used by clients to distinguish problem types, does not change with Accept-Language. Example: 400, 401, 403, 404, 500
timestamp	string	No			Timestamp is the time when the error occurred. ISO 8601 format. Example: "2026-04-03T12:00:00Z"
title	string	No			Title is a short, human-readable summary of the problem type. The same Type should always have the same Title (does not vary per instance). Example: "Invalid Request Parameters"
trace_id	string	No			TraceID is a distributed tracing identifier. Follows the W3C Trace Context standard. Example: "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01"
type	string	No			Type is a URI reference that identifies the problem type. When dereferenced, it should provide human-readable documentation. Example: "https://api.example.com/errors/invalid-request"