Release r202604
What's new
This release contains the following new or changed functionality:
Multiple authentications for HTTP and REST accounts
In release r202506, we introduced support for multiple authentication credentials on Xurrent accounts. This capability has now been extended to HTTP and REST accounts.
You can add multiple bearer tokens or OAuth client credentials to a HTTP or REST account using the "Add authentication" button in the account settings.
As with Xurrent accounts, when a package makes an API call using a HTTP or REST account, the least recently used credential is chosen, ensuring that credentials are rotated after each use. This allows the automator to distribute calls across these authentication credentials.
Automatic retry for HTTP and REST calls
HTTP and REST calls now automatically retry when a call fails due to a temporary issue on the remote server. The following scenarios are retried:
- Connection errors
The remote server cannot be reached, e.g. due to a timeout, connection refused, or connection reset. The number of retries depends on the type of error. - Server errors
The remote server returns an HTTP error status code (5xx). The call is retried up to 2 times to avoid temporary issues. - Rate limiting
The remote server responds with aRetry-Afterheader. The automator waits the indicated time before retrying. - GraphQL query cost limit
A GraphQL API signals that the query cost limit has been exceeded. The call is retried after the indicated wait time.
The retry behavior for HTTP and REST accounts only works if the account has been configured with a bearer token or with OAuth client credentials.
No changes to existing packages are needed.
Timeline
The deployments of the release will be performed on
| Environment | Date |
|---|---|
| Demo | Friday, February 13th |
| Production (automator.techwork.at) | Thursday, February 19th |
| Production | Tuesday, February 24th |
The deployment of the Production environments will be conducted outside of office hours (Central European Time Zone).