Top 10 common issues

1. Logo upload fails

• File too large (limit: 2 MB).
• Wrong format. Use PNG, JPG, or WebP. Not HEIC, not TIFF, not SVG with embedded raster.
• Browser permission revoked. Refresh the page.

2. Continue button disabled in onboarding

Look at the Still needed to continue hint above the button. It lists exactly what is missing — usually a logo, specialisation chip, or one of the required text fields. Click into the missing field, fill it, the button enables instantly.

3. Slug warning when changed

The slug determines the public URL. Changing it after publish breaks any link you already shared. The warning is intentional — proceed only if no shared links exist.

4. AI wizard says "extraction failed"

The prompt was too short or too vague. The model needs at least one hotel name and one price tier to anchor the extraction. Add detail and retry. If it fails twice in a row, fall back to manual entry on screen 2.

5. Package not appearing publicly

Check status. Draft packages are hidden. Set status to Active on the edit page or via the package list dropdown.

6. Cannot update enquiry status

If the enquiry shows a Sample badge, it is illustrative seed data — not a real lead. Sample enquiries are read-only by design. Submit a real enquiry to your own profile in Incognito to test the pipeline.

7. PDF will not generate

PDF rendering uses a server-side Chromium instance. The first call after a deploy can take 5–8 seconds (cold start). If the request times out, wait 10 seconds and retry — the second call usually succeeds.

If it still fails, the package is missing a required field for the brochure layout (price tier, hero image, or itinerary). Fill the missing field and retry.

8. Banner downloads as JSON instead of PNG

This is a browser issue, not a TourDock issue. The endpoint sets the right Content-Type, but some browsers (older Firefox versions) misinterpret it. Workaround: right-click the banner button, select Save link as, name the file with a .png extension.

9. Operator code not visible

Codes were added in a later migration. Operators who registered before that point see a Generate code banner on the dashboard. Click it; the code is generated and assigned. The banner disappears.

10. Profile completeness stuck below 100 %

Profile completeness counts: logo, cover (or branded fallback), description (≥ 100 chars), founded year, license, IATA, address, business hours, languages, website, at least one social handle. The two most-skipped are IATA (toggle on/off counts; the form needs an answer) and Cover photo (upload one or accept the gradient — accepting still completes the field).

If you have addressed every field above and still see < 100 %, refresh the page. The badge is cached for 5 minutes.