Skip to content

Troubleshooting

Your browser session may have expired. Sign in again with a Google or Microsoft identity associated with your TravelDB membership. If the provider says your account is not allowed, use the exact email address that received the invitation or contact the person who invited you.

Look for an unsaved message near the action:

  • Save structure before confirming structure.
  • Save any destination mapping after changing it.
  • Save corrections after changing pricing.

TravelDB prevents tab changes and later workflow actions from consuming unsaved data.

Extraction notes are informational. Compare the related value with the source document and correct the draft if necessary. A blocking publication problem is shown separately under Fix before publishing.

Some Rates Stores require each extracted rate to be mapped to a destination record. Return to the destination settings and add the missing mapping, or acknowledge that those rates should be omitted from this publication. See the selected Rates Store’s guide for its mapping rules.

Open History in the publish section. Do not assume that every write failed: publication may be recorded in smaller operations, and an interrupted request can leave an outcome unknown. Reconcile the listed changes with your Rates Store before repeating the publish.

Contact the TravelDB person who onboarded your organisation. Include:

  • What page you were on.
  • The button or action you used.
  • The supplier and document name.
  • The full error message and request ID, if shown.
  • Whether the same data is visible in your Rates Store.

Do not send passwords, API keys, or the contents of browser cookies.