Instalink already processes millions of requests every day with over 99.999% up time. Over the years this platform has exceeded our expectations for accuracy, reliability, and efficiency. However, we know it isn't perfect. Specifically, Instalink could be prone to memory allocation overruns at higher scales of data ingestion. This would make it difficult to pull in extremely large data sets during the execution of a data flow. We recognized this and knew that we could do better.

So we have been working tirelessly for the past two years to improve our processors by rebuilding them entirely from scratch. The processors have been rebuilt using Rust. This allows our processors to be much more memory efficient while still improving our processing performance. For the past six months we have been slowly rolling out the new version of Instalink to select customers. The results have been dramatic.

New Features in 1.22.1 include:

New Features in 1.21.0 include:

New Features in 1.20.4 include:

Added sample input support for database actions.Added view that shows the current status of all connector deployments for a specific connector. This shows the current version that has been deployed to every subscriber and when the connector update last propagated to that instance. Click "View Connector Deployment Statuses" on the project settings to access this view.

Bug Fixes in 1.20.4 include:

Fixed issue where process data inspector was performing operations for actions that were marked as SKIP.Removed empty link from the top level flow view for RUN_ACTION data flows. RUN_ACTION flows do not have an endpoint URL.Data flows with RUN_ACTION as the top action now correctly dsplay run statistics.Fixed an issue that made it impossible to properly reparent a cloned action.

Other changes in 1.20.4 include:

New Features in 1.20.3 include:

All Actions now track the history of modifications and which user made the changes. Click "Edit History" on the action's links sub tab to access this report for any specific action. The yellow warning icon in the data flow is now clickable. This directs the user to the warnings report for the action.

Bug Fixes in 1.20.3 include:

Fixed issue where it was possible to accidentally reparent an action during the create operation.Fixed issue where it was possible for the process data inspector to get stuck recursively loading connector data.Corrected the behavior of the ctrl clicks in the interface.

Other changes in 1.20.3 include:

Added documentation about memory management strategies to the Instalink website.

Bug Fixes in 1.20.2 include:

Fixed issue that could cause admin panel crash when a process doesn't have a project id set.Fixed issue where the connector data wasn't being processed correctly in the process data inspector.

Other changes in 1.20.2 include:

Disabled auto-scrolling to the process data inspector of recently opened actions.

Bug Fixes in 1.20.1 include:

Fixed issue where the table view couldn't be scrolled horizontally when loaded inside of a the main window while inline tabs are visible.

We sought to accomplish the following with the major 1.20.0 release:

Improve the ability of developers to create data flows.Remove the guesswork about how data flows will behave.Give developers real-time feedback about their processes as they are working on them.Make documentation readily available and easily accessible.

New Features in 1.20.0 include:

Rebuilt project management interface

The Problem with Error Log Notifications

While there are several actions that can be used in Instalink to directly alert an administrator to an issue with a data flow, such as "Respond with Error", "Send to URL", or "Send Message", there are situations where receiving a direct notification on service errors may not be ideal. For example, imagine a data flow where the administrator receives an email every time a call fails to send to an external API. This may initially seem to be an intuitive way to set up error notifications. However, the problem quickly becomes evident when the external API goes down and returns an error for each request. Indeed, a user may receive thousands of emails during a service outage if a data flow is set up to send an email to an administrator on every occurrence of a logged error.

Sending a notification on the error log should be used only in situations where the error is expected to be encountered infrequently.

New Features in 1.13.0 include:

Improved user interface for forms making it obvious whether or not a form submission was successful or not.Error response emails can now be delivered to the subscribers of a topic rather than a single email address.A new process flow action for delivering email and SMS messages to the subscribers of a topic.Items within a queue may be cancelled so that they will not be processed.An option was added to the "FTPS" action to skip validation of the server's SSL certificate.An options was added to "Listen" actions to automatically generate the necessary CORS headers and endpoints for accessing Instalink.io URLs in the browser.

Bug Fixes in 1.13.0 include:

The "prevent duplicates" feature for process queue items has been fixed.A problem where entering certain invalid URL strings into the "Send To URL" and "FTPS" actions could cause a processor to crash has been fixed.

Other changes in 1.13.0 include: