Overview
When a vendor stops accepting the login Daasity holds for one of your integrations, you now hear about it from the connection check, before your data goes missing. A temporary outage on the vendor's side is no longer reported as a login problem, and when the problem is with Daasity's own access, it comes to us instead of asking you to reconnect. An integration you turned on but never added to a workflow now gets a notification too.
What's fixed
Rejected logins are caught.
Some connection checks treated an expired or revoked login as working, so nobody heard about it until data stopped arriving. That's fixed for TikTok Shop, Klaviyo, Yotpo, AppLovin, Cin7 Core, Northbeam, Skio, Algolia, Narvar, Newstore, Avalara, Reddit, Facebook, Sailthru, Criteo, Google Analytics on BigQuery, Walmart Marketplace, Salesforce Service Cloud, and your database, S3 and SFTP sources. Any integration whose vendor rejects the login is now treated as a login problem. You get a "Reconnect needed" or "Couldn't reach the source" notification with a button to fix it.
Fewer false alarms.
ShopMy, Instacart Ads, Prodco, Shopify B2B and Iterable had reported a temporary outage on the vendor's side as a login failure. They no longer do.
Errors that tell you the fix.
Saving a GA4 integration whose Google login expired now asks you to reauthorize instead of showing an error. A TikTok Ads login with no access to any advertiser account explains the ways to fix it. A BigQuery connection missing a permission tells you which one.
History loads stop on a login problem.
If a history load runs into a login problem, it now stops and tells you, instead of carrying on or sitting in the queue with no error.
What's new
Integrations left out of a workflow.
If an integration is active but isn't part of any active workflow, Daasity isn't pulling its data. You now get an "Integration not in a workflow" notification, with a Review button to add it to a workflow. New integrations get 7 days before it appears.
What to expect
If one of your integrations now asks you to reconnect, its saved login had stopped working. Click Reauthorize, or Check connection for a database, and it starts loading again.
Notification Types lists every notification and what to do about it.