You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with the control API the docs for amqp/externa->target->message_ttl is "You can optionally override the default TTL on a queue and specify a TTL in minutes for messages to be persisted. It is unusual to change the default TTL, so if this field is left empty, the default TTL for the queue will be used."
However if I create a rule with a set TTL then update it and leave TTL empty. It keeps the TTL i specified on creation instead of reverting to queue default.
with the control API the docs for amqp/externa->target->message_ttl is "You can optionally override the default TTL on a queue and specify a TTL in minutes for messages to be persisted. It is unusual to change the default TTL, so if this field is left empty, the default TTL for the queue will be used."
However if I create a rule with a set TTL then update it and leave TTL empty. It keeps the TTL i specified on creation instead of reverting to queue default.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: