All Collections
Versions 3.0 and 2.0
Implement
All Products
What are the limitations of Data Hooks®?
What are the limitations of Data Hooks®?
Elisa Dinsmore avatar
Written by Elisa Dinsmore
Updated over a week ago

This article is for Flatfile's Portal 2.0, Portal 3.0, and Workspaces. If you'd like to check out the latest version of the Flatfile Data Exchange Platform, click here!

While Data Hooks® are an incredibly powerful tool, it is still important to remember that there are some limitations. We don’t want you to get frustrated trying to do something with a Data Hook that Data Hooks were not designed to do.

With that in mind, consider the following:

Data Hooks cannot, and were not designed to, access global data. In other words, Data Hooks can only access the data of the import they are acting on. Data Hooks cannot access, manipulate, or read data from previous imports.

When testing Data Hooks, errors, warnings, and comments will not appear in the Data Hook test environment.

The AWS Lambda service used to power Data Hooks has a 15 minute timeout. If processes hang, or other problems are encountered, the Data Hook itself may not be able to work on your data if it has been timed out of the AWS Lambda service. Data Hooks created in the UI and Data Hooks deployed from the Flatfile Platform SDK both use this service.

Did this answer your question?