0.17.1
StableSign-in is protected against automated abuse, and failed calls now record the app's own reference number.
Three changes, none of which alter how your AI client talks to FloConnector.
Sign-in is protected against automated abuse
Both sign-in surfaces, the dashboard and the page you see when connecting an AI client, are now protected by reCAPTCHA. There is no puzzle and nothing to click. You will see a small reCAPTCHA badge on those pages and nothing else changes.
It only guards sign-in. It never touches the data flowing through your connections, and if the check cannot be reached, you can still sign in.
Failed calls record the app's own reference number
When a connected app rejects a call, it usually returns its own reference for that exact request. That reference is the fastest way for the app's support team to find what happened, and until now it was thrown away.
It is now recorded against the failed call and shown in Activity, next to the error reason. It is also included in the CSV export, so raising a support ticket with a connected app is a matter of exporting the row and quoting the reference rather than describing the problem from memory.
We still store no request or response content. This is a reference number, not your data.
Fixes
An install link that had expired or already been used would send you back to it every time you signed in, instead of taking you to your dashboard. It now clears itself, and any link left over from before is cleared the next time you sign in.
