Scripts in data flows

Scripts are used as a supporting activity step in Document Flows and Data Lake Flows.

When a scripting step is activated at runtime, the incoming message content, message headers or constant value can be sent as a parameter to the code contained in the script for execution.

From the script code perspective, the input parameters are passed as the Input Variable name; the output message content and optionally also output message headers are generated from selected Output Variables.

Limitations

These are the script runtime limitations:

  • Maximum execution time of 15 seconds.
  • Scripts can process input payload up to 5 MB.
  • Scripts can output payload up to 5 MB.
  • Script memory limit up to 1000 MB.
  • Scripts access to external and online resources is prevented.

A script can only access the script code, the library dependencies attached to it, and the input payload passed at runtime.

Runtime errors and exceptions

During runtime execution of a script, if an error occurs a Confirm BOD is published because of these reasons:

  • Python exception.
  • Input Variable name was not used in the code.
  • Output Variable name was not used in the code.
  • The script does not exist. It was deleted while it was used in an active data flow.
  • The input payload exceeds the five MB limit.
  • The output payload exceeds the five MB limit.
  • The execution exceeded the 15 second runtime limit and timed out.
  • The script failed to execute after 10 retries.
  • The script failed to execute because of a memory limit.
  • The script failed to execute because of reduced networking resources.