Add changelog for February 2, 2025 #180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API Request Node, Improved Retries, and Enhanced Message Controls
HttpRequest Node Renamed to ApiRequest: The
HttpRequestworkflow node has been renamed toApiRequest, and can be accessed throughAssistant.model.workflow.nodes[type="api-request"]. Key changes:isAsyncflagThe
HttpRequestnode is now deprecated and will be removed in a future release. Please migrate to the newApiRequestnode.New Backoff and Retry Controls: You can now configure
Assistant.model.tools[type=dtmf].server.backoffPlanto handle failed requests with customizable retry strategies and delays.maxRetries(up to 10) andbaseDelaySeconds(up to 10 seconds)backoffPlanpropertyEnhanced Gather Node: The
Assistant.model.workflow.nodes[type=gather]node has been improved with the following changes:maxRetriesproperty to control retry attemptsconfirmContentpropertyImproved Message Controls:
Assistant.messagePlanhas been improved with the following changes:idleTimeoutSecondsmaximum from 30 to 60 secondssilenceTimeoutMessageto customize call ending due to silenceNew Distilled Deepseek Model with Groq: You can now select
deepseek-r1-distill-llama-70bwhen using Groq as the provider inAssistant.model[provider='groq']Edge Condition Updates: Edge conditions now require explicit matching criteria to improve workflow control and readability. Semantic edges must specify a
matchesproperty while programmatic edges require abooleanExpressionproperty to define transition logic.