Managing Integration Job Failures
Summary
Learn how to monitor, troubleshoot, and resolve integration job failures caused by authorization issues, maintenance modes, or quota limits.
To prevent log flooding and redundant system strain, Flxpoint monitors the health of your integration jobs. If a job fails repeatedly due to persistent errors, the system may automatically pause or terminate the scheduled job. This ensures that resources are not wasted on requests that are guaranteed to fail until an underlying issue is resolved.
Integration jobs typically fail due to external factors related to your sales channel or source. Understanding the error code helps you identify the necessary fix.
Error Type | Description | Typical Resolution |
|---|---|---|
403 Forbidden | Authorization has failed or the credentials lack sufficient permissions. | Update your API tokens or credentials in the integration settings. |
Maintenance Mode | The external platform is temporarily offline for updates. | Disable the job schedule manually until the platform returns to service. |
503 Service Unavailable | The external server is overloaded or down. | Verify the status of the source/channel and retry once their service is restored. |
Quota Limits | You have exceeded the API call limits allowed by the external platform. | Reduce the frequency of your scheduled jobs or upgrade your plan with the external provider. |
When a job is paused or failing, follow these steps to restore the sync:
Identify the root cause. Review the job logs to see the specific error code and message returned by the source or channel.
Disable the schedule. If the issue requires time to fix, navigate to the job settings and disable the schedule to prevent further logged failures.
Update credentials. If the error is authorization-based, re-enter your API keys, tokens, or login credentials and save the settings.
Test the connection. Use the Test Connection action (where available) to verify that Flxpoint can communicate with the external system.
Reactivate the job. Once the connection is successful, re-enable the job schedule or run the job manually to ensure data is flowing correctly.
Note: Log management improvements now prevent redundant upload failure entries from flooding your history during repeated failures, making it easier to find the original error.