FlowmageDocs

Twinfield errors

The codes Twinfield steps can stop a run with, each with its fix and what happened.

  • TWINFIELD_AUTH

    Connect it again under Manage → Connections.

    Twinfield rejected the sign-in.

  • TWINFIELD_CLUSTER_UNKNOWN

    Press Test on the connection.

    Flowmage does not know this Twinfield login's cluster yet.

  • TWINFIELD_FORBIDDEN

    This Twinfield login may not do that in this company.

  • TWINFIELD_INVALID_CONFIG

    Its own message says which part.

    This Twinfield node is not filled in yet.

  • TWINFIELD_INVALID_REQUEST

    Check the element names and the characters in it.

    The Twinfield document cannot be sent as written.

  • TWINFIELD_INVALID_RESPONSE

    Check the connection.

    Twinfield answered something that is not a SOAP document.

  • TWINFIELD_NO_COMPANY

    Fill one in.

    Twinfield needs a company code on every call but the offices list.

  • TWINFIELD_REFUSED

    The field or code it objected to is in the detail.

    Twinfield took the call and refused it.

  • TWINFIELD_REQUEST

    Check the node's settings.

    Twinfield refused the request.

  • TWINFIELD_RESPONSE_TOO_LARGE

    Ask per period, or for fewer columns.

    Twinfield answered more data than a run can parse.

  • TWINFIELD_THROTTLED

    An unregistered one gets 25 credits a minute per administration.

    Twinfield is throttling this client.

  • TWINFIELD_TOO_MANY_LINES

    Split it.

    A Twinfield transaction carries at most 1,000 lines.

  • TWINFIELD_TOO_MANY_RESULTS

    Narrow the period or the search.

    Twinfield returned more rows than a run can carry.

  • TWINFIELD_UNAVAILABLE

    Try again once it is back.

    Twinfield could not be reached.