FlowmageDocs

Exact Online errors

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

  • EXACT_AUTH

    The connection needs to be reconnected.

    Exact Online refused the session.

  • EXACT_FORBIDDEN

    This user may not see it in this division.

    Exact Online refused the resource.

  • EXACT_INVALID_BODY

    Give Exact Online JSON fields.

    The record body is empty or not an object.

  • EXACT_INVALID_CURSOR

    Paste an earlier Next cursor, or clear it.

    The Cursor is not a next page of this resource.

  • EXACT_INVALID_ORIGIN

    Fix it under Manage → Connections.

    The Exact Online country is not one of its sites.

  • EXACT_INVALID_RESOURCE

    Write it as Exact Online spells it.

    The resource path is empty.

  • EXACT_INVALID_RESPONSE

    Check the connection.

    Exact Online answered something that is not JSON.

  • EXACT_NOT_FOUND

    Exact Online has no record by that id.

  • EXACT_NO_DIVISION

    Set a division, or reconnect it.

    This connection has no administration to act in.

  • EXACT_REQUEST

    Check the resource path and the values.

    Exact Online refused the request.

  • EXACT_RESPONSE_TOO_LARGE

    Ask for fewer fields, or a smaller page.

    Exact Online answered more data than a run can parse.

  • EXACT_THROTTLED

    The window has to reset.

    Exact Online is throttling this division (60 calls a minute).

  • EXACT_TOO_MANY_ROWS

    Narrow the filter, or page the request.

    Exact Online returned more rows than a run can carry.

  • EXACT_UNAVAILABLE

    Try again once it is back.

    Exact Online could not be reached.