Routing API Problems PTV Developer (TMS)

Resolved
Resolved

PTV has resolved the issue and PTV Developer should be working again. Routing should now function as normal.

If you applied the workaround, please restore your original settings in Transport Setup:

  1. Set Default Activity Calculation Type back to its previous value.
  2. Re-enter the values you noted down in the xServer xMap URL, xServer xLocate URL, xServer xRoute URL and xServer Profile fields.

Trips created during the outage may be missing driving kilometres and times, and ETAs may not have been calculated. These trips can be recalculated once the settings are restored.

If you still experience problems after restoring your settings, please contact Boltrics Support. We apologize for any inconvenience.

Updated

Workaround To keep planning while the outage lasts, you can temporarily bypass PTV routing in Transport Setup:

  1. Under Trip Activity Calculation, set Default Activity Calculation Type to Default.
  2. Under Integrations, clear these four fields: xServer xMap URL, xServer xLocate URL, xServer xRoute URL and xServer Profile. Note down the current values first, so you can restore them later.

With this workaround, the system creates trips without driving kilometres and driving times. ETAs will not be calculated successfully.

Once PTV has resolved the issue, restore the original settings to bring routing back to normal.

Investigating

Customers using PTV Developer may currently experience a partial outage. The issue originates at PTV, who are actively investigating it and working on a solution. We are monitoring the situation and will update this page as soon as we have more information. We apologize for any inconvenience.

Began at:

Affected components
  • External Boltrics
    • Other