Troubleshoot channel setup

Resolve the first failed prerequisite. Repeating activation or creating another property can turn a recoverable error into a duplicate connection.

Holidario Channel Manager is not ready#

If Settings > Holidario Channel Manager says that the service is being set up:

1. confirm that you are in the correct team;
2. check that the plan includes Channel Manager;
3. do not look for or enter an external API key;
4. ask for help with the team, screen, and time.

The operation is pending or failed#

Open the infrastructure panel and review the operation state.

• No previous attempt: select Sync Missing Rentals once.
• Sync started: wait; do not submit the same work repeatedly.
• Last sync failed: retain the exact message, review the name, property, capacity, and cleaning fee, then retry once.
• Partial technical data: support is required. Creating another listing cannot repair it.

No rooms or rates are found#

On the OTA card:

1. select Edit listing data;
2. compare the identifier with the actual listing;
3. correct the name, identifier, or URL;
4. save and start the connection again.

If the identifier is correct but no room appears, ask for help. Include the platform, property, non-sensitive identifier, and time.

The connection fails#

Holidario retains the latest error on the listing card and creates a task to correct its details.

1. retain the exact error text;
2. confirm that infrastructure is complete;
3. confirm that pricing and future months are configured;
4. correct listing details when the error identifies them;
5. retry once.

Holidario shows Connected only when the provider contains the exact mapping between this operation's listing and rate plan. Property membership in a shared channel is not sufficient. If an earlier attempt added the property but did not finish its mapping, the card continues to offer Connect Airbnb so the missing step can be resumed. When the Airbnb account and property are already connected, this retry creates the missing mapping without reauthorizing Airbnb or rewriting the shared channel. If a legacy shared channel uses an older group for the same agency, Holidario first adds the property to that group without removing it from its current group; it blocks the retry if the channel contains properties from another team.

Do not send passwords, cookies, API keys, or verification codes in a support request.

The connection exists but is inactive#

This is the expected state of a new connection. Complete the pre-activation checklist. Do not disconnect and recreate it solely to change its state.

Disconnect a listing from a shared channel#

Disconnect applies to the listing on the open operation. When several listings from the same Airbnb account share one provider channel, Holidario removes only this listing's mapping and property; it preserves the channel and every sibling listing mapping.

If Holidario cannot safely identify the exact mapping or encounters an unsupported shared channel type, it blocks the action and preserves the complete channel. Do not use Disconnect as a diagnostic test: review calendars and bookings first, and retain the message if the action is blocked.

The state is unclear#

Do not repeatedly select activate, deactivate, or disconnect. Refresh once and check:

• the OTA card indicator;
• Airbnb session or Booking session, which confirms account access but not the Channel Manager mapping;
• the activation Pending Task;
• dates and prices in the calendar;
• the listing state on the OTA.

If these sources disagree, stop and ask for help before allowing new bookings.