FlowmageDocs

Common errors

The codes any step can stop a run with, each with its fix and what happened.

  • APPROVAL_LIMIT

    Decide or cancel some before asking for more.

    This workspace has as many open approval requests as it may.

  • APPROVAL_NO_RECIPIENT

    Every person it names has left the workspace, or none was named.

    Nobody can answer this request.

  • APPROVAL_REDACTION_UNAVAILABLE

    The step is retried on its own.

    This run could not check the request for secrets before sending it, so nothing was sent.

  • CANCELLED

    This run was cancelled.

  • COLLECTED_TOO_LARGE_FOR_NODE

    Loop over that list instead.

    A step reads a loop's collected list too long to load at once.

  • CONCEPT_ONLY_IN_TEST

    Activate a version to run in production.

    Draft runs only work in the test environment.

  • CONCURRENCY_LIMIT

    Wait for one to finish, or upgrade the plan.

    This workspace has too many runs going at once.

  • CONNECTION_BROKEN

    Re-enter them under Manage → Connections.

    The provider rejected the stored credentials.

  • Open the connection and grant it.

    This provider needs a one-time consent.

  • CONNECTION_DECRYPT_FAILED

    Re-enter them under Manage → Connections.

    This connection's stored credentials could not be read.

  • CONNECTION_MISSING

    Add them under Manage → Connections.

    This connection has no credentials for this environment.

  • CONNECTION_NOT_FOUND

    Pick another in the node's settings.

    This connection no longer exists.

  • CONNECTION_NOT_SELECTED

    Pick one in the node's settings.

    No connection is selected.

  • CONNECTION_RECONNECT_REQUIRED

    Reconnect it under Manage → Connections.

    This connection's sign-in is no longer valid.

  • CONNECTION_TENANT_NOT_FOUND

    Check it under Manage → Connections.

    The address answered a web page instead of data.

  • CONNECTION_UNREACHABLE

    Try again in a moment.

    The provider could not be reached.

  • EGRESS_BLOCKED

    Try the node's fixed IP address option.

    The target system blocked the request from our network.

  • EGRESS_REFUSED

    Check the node's address and network settings.

    This request was not allowed to leave Flowmage.

  • EGRESS_TRANSPORT

    Check that the address is right and the system is up.

    The target could not be reached.

  • ENGINE_INTERNAL

    Quote this code if it repeats.

    Flowmage hit an internal fault on this run.

  • EXPRESSION_ERROR

    Check the field it names.

    An expression in a node's settings could not be evaluated.

  • FILE_ARCHIVED

    Restore it under Storage → Files.

    A file this flow reads is archived.

  • FILE_CONTENT_INVALID

    Check its format.

    A file's contents are not what the node expected.

  • FILE_LIST_TOO_LARGE

    Narrow the prefix, or list them page by page.

    There are too many files to list at once.

  • FILE_NOT_FOUND

    Check the name under Storage → Files.

    A file this flow reads does not exist.

  • FILE_STORE_MISCONFIGURED

    Tell an operator.

    File storage is not configured for this deployment.

  • FILE_TEXT_TOO_LARGE

    Read it in parts with Offset and Length, or allow a partial read.

    This file is larger than one read carries.

  • FILE_TOO_LARGE

    Work with it in parts.

    A file is too large for a run to carry.

  • FLOW_BUSY

    This run was skipped.

    This flow runs a limited number at a time and is busy.

  • FLOW_QUEUE_FULL

    Wait for it to drain, or raise that flow's limit in its Flow settings.

    A flow's run queue is full.

  • INVALID_LOOP_ITEMS

    Check the loop node's items field.

    A loop did not receive a list of items.

  • ITERATIONS_EXCEEDED

    Narrow the list before the loop.

    A loop had more items than a run allows.

  • JS_ERROR

    Its own message says what went wrong.

    A JavaScript node threw.

  • JS_INPUT_TOO_LARGE

    Trim the upstream output, or route large payloads through files.

    A JavaScript node was handed more than it accepts.

  • JS_OUTPUT_TOO_LARGE

    Return less, or write large payloads through a file node.

    A JavaScript node returned more than a run may carry.

  • LOOP_COLLECT_TOO_LARGE

    Collect one field, not the whole step.

    One round of a loop collected more than a round may hold.

  • LOOP_ITEMS_TOO_LARGE

    Pass less data per item.

    A loop's list of items is too large to carry.

  • MAIL_DAILY_LIMIT

    Sending resumes at 00:00 UTC, or send through your own AWS SES connection.

    Today's flow emails through the platform sender are used up — this workspace's, its organization's or the Free plan's.

  • MULTIPART_INVALID_CONTENT_TYPE

    The file's content type is not a media type. Use a value such as image/png or application/pdf, and check the field it comes from.

  • NODE_RESTARTS_EXHAUSTED

    It needs to be fixed, not re-run.

    A node ended the run environment every time it was tried.

  • NODE_TIMEOUT

    The system it calls may be slow.

    A node ran past its time limit and was stopped.

  • NODE_UNEXPECTED

    Re-run to see if it repeats.

    A node failed with an error it does not describe.

  • NO_ACTIVE_VERSION

    Activate a version first.

    Nothing is deployed to this environment yet.

  • OUTPUT_NOT_SERIALIZABLE

    Return plain data instead.

    This node returned a value that cannot be stored as JSON.

  • OUTPUT_STORE_UNAVAILABLE

    Flowmage's output store could not be reached while this step saved or read its data.

  • OUTPUT_TOO_LARGE

    Return less, or write a file.

    A node returned more data than a run can carry.

  • OUTPUT_TOO_LARGE_TO_REFERENCE

    That output is kept and downloadable.

    An expression here reads an earlier output too large to load.

  • PAGE_CURSOR_REPEATED

    Run it again, or page it in a loop.

    The system pointed back at a page this read had already followed.

  • PAGE_RATE_WINDOW_FULL

    The read waits for room and resumes at the page it stopped before.

    The system's rate window was full.

  • PATH_SEGMENT_INVALID

    Flowmage refused it before sending anything.

    An id on this node is empty or is not a single id.

  • PLAN_LIMIT_REACHED

    Upgrade to add more.

    Your plan's limit is reached.

  • PLAN_NEWER_THAN_BUILD

    The answer is kept and lands when it runs.

    This run waits for a newer build of Flowmage.

  • PLAN_NOT_RUNNABLE

    Deploy it again.

    This flow's deployed version can't run on this build.

  • RESPONSE_TOO_LARGE

    Ask it for less, page by page.

    A system answered with more data than a run can carry.

  • RUN_LIFETIME_EXCEEDED

    Shorten its waits and delays.

    This run was still not finished 100 days after it started.

  • SCHEMA_READ_ONLY

    A replay only shows what the run did.

    Replaying a node's configuration may not write a schema.

  • SCHEMA_TOO_LARGE

    Use a table or a file.

    A schema would grow past what one document may hold.

  • SECRET_MISSING

    Add it under Manage → Secrets.

    A secret this flow needs is not set.

  • SES_SEND_FAILED

    Its own reason is in the detail.

    The mail service refused this message.

  • SQL_AUTH_FAILED

    Fix them on the connection under Manage → Connections.

    The database refused the user name or password.

  • SQL_CONNECTION_LOST

    A statement that changes data may still have run, so check first.

    The database connection dropped mid-query.

  • SQL_CONNECT_FAILED

    Check the host, port and that it lets in both fixed IP addresses.

    The database could not be reached.

  • SQL_PARAMS_INVALID

    Parameters must be a list of at most 1,000 plain values.

    A parameter could not be sent.

  • SQL_QUERY_FAILED

    Its own message is in the detail.

    The database refused the query.

  • SQL_READ_ONLY_VIOLATION

    Choose Execute statement if the change is intended.

    This query tried to change data in Select rows.

  • SQL_RESULT_TOO_LARGE

    Select fewer columns or rows.

    The query's result is larger than a run can hold.

  • SQL_TIMEOUT

    A statement that changes data may still have run, so check first.

    The database did not answer in time.

  • SQL_TLS_FAILED

    Check the connection's encryption setting and certificate.

    The encrypted connection to the database failed.

  • SQL_TOO_MANY_ROWS

    Add a LIMIT or WHERE, raise Max rows, or return the first rows.

    The query returned more than Max rows.

  • SUBFLOW_BUSY

    Try again later.

    The flow this node calls skips a run while it is busy, so the call did not start.

  • SUBFLOW_CANCELLED

    The subflow this node called was cancelled before it finished.

  • SUBFLOW_CYCLE

    Call a different one.

    Calling this flow would loop back to a flow already in the chain.

  • SUBFLOW_DEPTH

    Call the flow from higher up.

    This call would nest subflows deeper than a run allows.

  • SUBFLOW_DRAFT_INVALID

    Fix it there, or call its test version.

    The draft of the flow this node calls cannot run.

  • SUBFLOW_FAILED

    Open its run to see why.

    The subflow this node called failed.

  • SUBFLOW_LOST

    Re-run to call it again.

    The subflow run this node was waiting for no longer exists.

  • SUBFLOW_NOT_CALLABLE

    Pick another.

    The flow this node calls is gone.

  • SUBFLOW_PARAMS_INVALID

    Check the node's parameters.

    A value passed to the subflow does not fit its parameter.

  • SUBFLOW_RESUME_URLS_EXCEEDED

    Return the decision, not the link.

    This run took more resume links from its subflows than it can hide.

  • TABLE_BATCH_TOO_LARGE

    Write it in batches.

    This write touches more rows than one call allows.

  • TABLE_CELL_INVALID

    Check the node's column mapping.

    A value does not fit its column's type.

  • TABLE_FILTER_INCOMPATIBLE

    Check the filter rows.

    A filter does not fit its column's type.

  • TABLE_FILTER_INVALID

    Check the filter rows.

    A filter on this read is not valid.

  • TABLE_IDEMPOTENCY_CONFLICT

    The first one stands.

    The same write was replayed with different values.

  • TABLE_REQUIRED_MISSING

    Check the node's column mapping.

    A required column got no value.

  • TABLE_ROW_CONFLICT

    Re-read it and try again.

    This row was changed by something else mid-run.

  • TABLE_ROW_NOT_FOUND

    It may have been deleted.

    A row this flow updates no longer exists.

  • TABLE_ROW_TOO_LARGE

    Store the bulk as a file.

    A row is larger than a table row may be.

  • TABLE_TOO_MANY_ROWS

    Narrow the filter, or return the first rows and continue with the cursor.

    This select matched more rows than one step returns.

  • TABLE_UNIQUE_VIOLATION

    Write a different value, or update that row instead.

    Another row already holds this value in a column that takes unique values.

  • TABLE_UNKNOWN_COLUMN

    Check the table's definition.

    A column this flow writes does not exist.

  • UNKNOWN_SIDE_EFFECT

    The other system may have received it, so check there first.

    A platform update interrupted a node mid-call.

  • WAIT_TIMED_OUT

    Nobody answered this step before its deadline, and it is set to fail when that happens.