Boston 4.3.6
π Release Date: January 31, 2025 - π Next Release Date: February 7, 2025
π Highlights of this Release
The Autom Mate 4.3.6 release delivers critical authentication fixes and stability improvements. A major issue where OAuth2 app client credentials failed to refresh tokens has been resolved, ensuring seamless authentication and uninterrupted API integrations. Additionally, an issue affecting MS Teams Autom executions has been addressed, preventing unnecessary deletion of Redis records when custom actions with stop operations are used. These fixes enhance token management, API stability, and workflow reliability, reducing unexpected failures and improving system performance.
π
±οΈ Bug Fixes
π OAuth2 Client Credential Token Refresh Issue
Previously, OAuth2 client credentials were not refreshing tokens correctly, causing authentication failures in API-based integrations. If an expired client credential was used in an Autom, the system attempted to refresh the token but encountered an error, preventing successful authentication. This issue has now been fully resolved to ensure uninterrupted operation.
π MS Teams Autom Stop Action Redis Record Deletion Fix
Previously, in MS Teams Autom executions, when a stop action was triggered, the system deleted the Redis record storing MS Teams conversation details. However, if a custom action containing a stop operation was used within an MS Teams Autom, this also attempted to delete the Redis record, leading to unexpected errors and conversation data loss.
Detailed Version
π OAuth2 App Client Credential Token Refresh Issue
Previously, OAuth2 app client credentials were not refreshing tokens correctly, causing authentication failures in API-based integrations. If an expired client credential was used in an Autom, the system attempted to refresh the token but encountered an error, preventing successful authentication. This issue has now been fully resolved to ensure uninterrupted operation.
β Fixes & Improvements:
Implemented automatic token refresh logic to ensure valid tokens are always available.
Resolved errors occurring when attempting to refresh expired client credentials.
Enhanced error handling to detect and resolve token expiration issues proactively.
Optimized OAuth2 client session management, preventing disruptions in API authentication.
With this fix, OAuth2-based applications now maintain continuous authentication, reducing downtime and ensuring smoother integration workflows, even when tokens expire.
π MS Teams Autom Stop Action Redis Record Deletion Fix
Previously, in MS Teams Autom executions, when a stop action was triggered, the system deleted the Redis record storing MS Teams conversation details. However, if a custom action containing a stop operation was used within an MS Teams Autom, this also attempted to delete the Redis record, leading to unexpected errors and conversation data loss.
β Fixes & Improvements:
Restricted Redis record deletion to only occur in the main Automβs stop action, preventing errors when using custom actions.
Ensured conversation details remain intact unless explicitly stopped in the main Autom.
Improved MS Teams Autom execution stability, preventing unintended data loss in custom workflows.
With this fix, MS Teams Automations now handle stop actions correctly, ensuring conversation details are managed reliably without unexpected deletions.
Last updated
Was this helpful?