Flowmage v4.11.5 – Patch Notes

Bullhorn Node: Automatic Retries
When Bullhorn has a temporary problem, the Bullhorn node now tries again instead of failing the flow straight away.

• A new Retry section under Advanced sets how many times a failed call is repeated, from 0 to 3. The default is 2, and 0 turns retries off
• Retries wait 2s, 5s and then 10s, so Bullhorn gets time to recover between attempts
• You choose which status codes trigger a retry: 429 Too Many Requests, 502 Bad Gateway, 503 Service Unavailable, 521 Web Server Is Down, 522 Connection Timed Out and 523 Origin Unreachable. Codes left unchecked are never retried
• Only codes that mean Bullhorn did not process the request can be selected. Retrying a create, update or delete therefore never makes duplicates. Codes like 500, 504, 520 and 524, where the request may already have gone through, are left out on purpose
• Retries apply to the whole call: the login discovery, the REST login, the request itself, and the second request after an expired session is refreshed
• Existing Bullhorn nodes get the defaults automatically (2 retries on all six codes). You don't need to change anything, and you can adjust the setting per node
• Error messages are easier to read. The status code now comes with a plain explanation, for example 503 - Bullhorn is temporarily unavailable, and the number of attempts when retries were used, for example (after 3 attempts)

Fixes

• Duplicating an AFAS node works again. AFAS nodes store their settings in a different place from other nodes, and copying one failed before this fix

Other Improvements
Minor bug fixes and performance optimizations