Package not found error in production, although function works in development environment

Package not found error in production, although function works in development environment

This means the packages aren't installed within the functions folder. In the local debugging environment, this issue doesn't occur because packages may be available globally. Please make sure packages are present within the respective functions folder.
    • Related Articles

    • Environment variables for testing

      In order to test your function in local debugging, either you can add the environmental variables in your local machine or you can add it in your .env file inside your functions folder and access the same.    In order to access the environment ...
    • How to create a folder in the File Store in the production environment?

      You can create folders using Catalyst SDK’s only in the development environment. The folders cannot be created through Catalyst SDK methods in the production environment. Hence, we would suggest you to create the folders in the Filestore only from ...
    • Class to be executed Could not be found

      The mentioned error “Class to be executed Could not be found” occurs only if the class file for your function code is missing. If you had uploaded the code via the Catalyst Console, kindly make sure you have uploaded it along with the class files to ...
    • Catalyst Data Store tables are empty in production

      We would suggest you to use the Catalyst CLI/Bulk Write API to perform the bulk write operation in your table in the production environment. You can export the same from development and import it into production. Please check this link for more ...
    • Catalyst Functions Class not found error

      Kindly do check on the following points.  Kindly make sure you have uploaded your Java function with all the complied class files.  If the class files are present, then kindly make sure you have provided the relative path of the main class properly ...