If one of your transactions is showing a “Failed” sync status, it is likely due to one of the following errors.
- APLOS_API_ERROR: There was a problem connecting to Aplos. Please wait a few minutes and try syncing the transaction again. If the issue continues, reach out to Keela Support so we can investigate further.
- NO_IMPACT_AREA_PURPOSE_MAPPING: This transaction’s Impact Area has not been mapped to a Purpose in Aplos. To fix this, go to your Aplos Sync Settings and create a mapping for the Impact Area used in this transaction.
- NO_DEFAULT_PURPOSE: A default Purpose has not been selected in your Aplos Sync Settings. Transactions without an Impact Area need to be mapped to this default Purpose. Please select a default Purpose in Aplos, then try syncing again.
- DATE_IN_CLOSED_PERIOD: The transaction falls within a closed accounting period in Aplos. This transaction will not sync unless the period is reopened.
- UNHANDLED_ERROR: Something went wrong while trying to sync this transaction. Please wait a few minutes and try again. If the problem persists, contact Keela Support so we can investigate further.
- NO_PAYMENT_PROCESSOR_ACCOUNT_MAPPING: This transaction's Payment Processor has not been mapped to an Aplos Account. To fix this, go to your Aplos Sync Settings and create a mapping for the Payment Processor used for this transaction, then try syncing again.