A concert is moved
- The request follows Bandsintown (one driving link, one artist, no client, date ahead) — the request and linked BIO events move to the new date, and the old date is freed.
- The request has a client, is shared by several artists, has several driving sources, only observes the concert, the artist has left the agency, the request has passed or the performance is recorded — the request stays as it is; the agency sees a “moved” flag and gets a notification. Changing the date is up to the agency — it doesn’t need to unlink the request from Bandsintown for that — and if it does, the client side is notified of the new date. More: locked fields.
If the new date has holds or is taken by another request, the agency gets a separate warning. Holds aren’t released.
A concert disappears
Bandsintown has no “cancelled” status, so a concert counts as gone after two loads in a row, and only if its date is ahead. Then:
- a locked single-artist request without a client and with no money received is declined;
- otherwise — a “cancelled” flag and a notification to the agency.
Notifications
The agency (respecting regions) and the artist get one notification per sync: a specific message for one change or a summary for several — bell, push and email.
A concert link in a BIO event
If you paste a Bandsintown concert link into a BIO event, the event takes the concert’s data. Possible errors:
- concert not found among your concerts — the event is handled as a regular one;
- another artist’s concert — it won’t reach booking;
- another request already follows this concert — one concert, one request;
- a locked concert drives the request — the BIO edit wasn’t applied.
More: locked fields, flags on a request.