Production Version 5.144.0 (21 November 2026)
This release makes syncing more reliable after a Reconnect and during bulk edits. Nothing needs to be reconnected or approved again.
What is new
No more lost messages after a Reconnect
When an admin clicks Reconnect on a connector, the partner site could refuse comments and status updates for a few minutes, and those changes were lost. Hooq now notices the refusal, picks up the new connection details and sends the change again once. Changes made right after a Reconnect now arrive.
Bulk edits are handled more smoothly
When many work items change at once, for example through a bulk edit or an automation rule, Hooq now does about half as much storage work per work item. If the platform asks Hooq to slow down, the change is retried a few minutes later instead of failing.
An extra check on who is sending
Hooq now also checks that each message comes from the partner site the Hooq's own connector is paired with. In this release the check only records a note for our team when the two differ; it does not refuse anything, so existing Hooqs keep working exactly as before.
Good to know
- A change made in the first minute after a Reconnect can arrive a few seconds later than usual, because it is sent a second time.
- If the partner site answers "too many requests" while a comment is being copied, that comment can still be missed. This is not new in this release.
Want to raise a ticket? Click here (opens in a new tab)
