Negative Flows

The Mambu Process Orchestrator (MPO) processes handle and record all errors generated during different phases of the connector: from extracting the data, performing transformations, to posting the dimension values and the journal lines into Microsoft Dynamics 365 Business Central.

Each negative use case is handled differently depending on what entity, dimension value or journal line, is sent to Business Central and depending on the phase of processing where the issue occurs.

Dimension values

If an error occurs during processing and posting of a dimension value, the following steps are executed automatically:

• The Business Central API call is retried a number of times. This number can be configured in the setup phase.
• Error details - such as errorProcess, errorMessage, errorSource, and errorCode - are stored in the Failed dimension values SD state diagram.
• A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Depending on the Mambu entity type and on the approach used for posting the dimension value in Business Central, the following error handling cases exists:

• Initial sync flow:
  • Entity types handled: branch, loan products, deposit products, clients, groups, loan accounts, and deposit accounts.
  • The unposted dimension values should be manually posted.
• Daily sync flow:
  • Entity types handled: branch, loan products, and deposit products.
  • The unposted dimension values should be manually posted.
  • The journal lines processing and posting is not started. After posting all dimension values, the Manual trigger process should be manually started in MPO to process and post the journal lines in Business Central.
• Real time sync flow:
  • Entity types handled: clients, groups, loan accounts, and deposit accounts.
  • The unposted dimension values should be manually posted, as soon as possible, and preferably on the same day when the entity item is created.

Error codes handled in retry mechanism

The errors handled by the POST Dimension Value Business Central API call are:

• Errors that involve a custom number of attempts:
  • HTTP codes:
    • 408 Request Timeout
    • 429 Too Many Request
    • 500 Internal Server Error
    • 502 Bad Gateway
    • 503 Service Unavailable
    • 504 Gateway Timeout
  • Specific Business Central errors:
    • Category: Internal_*
    • Description: ServerError
• Error that involves a single attempt:
  • HTTP code: 401 Unauthorized. In this case the Authorization Credentials are again retrieved from the Config SD and the API request retried.

Journal lines

Journal lines processing can be grouped into three phases: retrieving, enriching, and posting the journal lines.

Depending on the phase in which the error occurs the following error handling cases exist:

Retrieve journal lines flow

If an error occurs during this phase, the following steps are executed automatically:

• The Mambu API call is retried a number of times. This number can be configured in the setup phase.
• Error details - such as errorProcess, errorMessage, errorSource, and errorCode- are stored in the Journal Lines processing errors SD state diagram.
• The queue where the journal lines batches are stored is emptied.
• A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error codes handled in retry mechanism

The POST Search Journal Lines Mambu API call errors that involve a custom number of attempts are:

• HTTP codes:
  • 408 Request Timeout
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout

Enriching journal lines flow

If an error occurs during this phase, the following steps are executed automatically:

• The Mambu API calls are retried a number of times. This number can be configured in the setup phase.
• Error details - such as errorProcess, errorMessage, errorSource, and errorCode - are stored in the Failed dimensions attachment to JL SD state diagram.
• A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error codes handled in retry mechanism

The Mambu API calls errors that involves a custom number of attempts:

• HTTP codes:
  • 408 Request Timeout
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout

Posting journal lines flow

If an error occurs during this phase, the following steps are executed automatically:

• The Business Central API call will be retried a number of times. This number can be configured in the setup phase.
• Error details - such as errorProcess, errorMessage, errorSource, and errorCode - are stored in a Failed journal lines SD state diagram.
• A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error codes handled in retry mechanism

The POST Journal Line Business Central API call errors handled are:

• Errors that involve a custom number of attempts:
  • HTTP codes:
    • 408 Request Timeout
    • 429 Too Many Request
    • 500 Internal Server Error
    • 502 Bad Gateway
    • 503 Service Unavailable
    • 504 Gateway Timeout
  • Specific Business Central errors:
    • Category: Internal_*
    • Description: ServerError
• Error that involves a single attempt:
  • HTTP code: 401 Unauthorized. In this case the Authorization Credentials are again retrieved from the Config SD and the API request retried.