Overview
This article is part of a four-article collection that provides a high-level overview of how to troubleshoot common issues with the Pacejet Shipping For NetSuite Bundle 20.x and higher. If you are still unable to resolve an issue after consulting these documents, please contact your Pacejet support representative.
Other Troubleshooting Topics
Troubleshooting the Update/Webhook Process
Webhook Subscriptions
When a delivery order is shipped or quoted within Pacejet, the Webhook process is used to contact NetSuite to notify of the changes that need to be made to the transaction record. Part of this process requires there to be Webhook Subscriptions created. These are found in Pacejet under Tools, API, Web Hooks, Subscriptions.
There Should be Five Records All with the Same URL
If you don't see all five, any of the URLs are different from another, or if any of them are missing their lightning bolt icon, then they need to be evaluated to ensure they are correct or there aren't any problems with Netsuite's Webhook.
If the URLs don't match each other or there are no records, then the Webhook Event Subscriptions need to be created. Please contact Pacejet Support to have these generated.
If the Lightning Bolt is Missing
If the lightning bolt is missing from one of the records, then there may be an issue with the webhook in Netsuite which has caused our webhook system to deactivate the subscription due to too many errors. If this is the case, you can first click the disabled event's title and enable the record.
Attempt to reprocess the transaction in question to try the update again.
If Problems Persist, Review the Webhook Log
If problems persist, you can review the webhook log to see if any recent webhook calls resulted in errors by clicking on the Web Hook Subscription page's left navigation notepad icon.
The log page will display the most recent webhook attempts and their status. If there are numerous statuses with a 500, there is an issue with the NetSuite side and will need to be reviewed.
The webhook script, customscript_pacejet_integration_webhook, is the script that is called when an update is sent from Pacejet to NetSuite. For issues where you are expecting an update in NetSuite from Pacejet that doesn't happen, this will be the first script you check.
If a shipment is big - the webhook script allows for more governance for updates. We use a schedule script, customscript_pacejet_schedule_int, so packages can be updated in the background.
This process verifies the data that is passed from NetSuite matches what was received by Pacejet. It is called when an update occurs and when the webhook is called inside of Pacejet.
To find this script follow the directions below.
Select Customization, Scripting, Scripts.
Select Suitelet from the TYPE menu, and, under SCRIPT FILE, select pacejet_IntegrationWebHook.js.
Select View.
The Webhook Even Log in Pacejet
The webhook event log inside of Pacejet shows you when an event occurred.