When the source changes the request itself
For a single-artist request without a client that is driven by a calendar event, a locked Bandsintown concert or a BIO event:
- the event is moved — the request moves to the new date and the old date is freed;
- the event disappears in two loads in a row (calendar, Bandsintown) or is deleted from BIO — the request is declined with the reason noted, and the date is freed;
- the agency gets one notification per load listing the changes.
If the new date is already taken by another request of the same agency, the agency gets a single notification about the move with a warning: “The new date is already taken by your request No. N”. Check both requests and decline or move the extra one.
When the source only sets a flag
The source doesn’t move or cancel the request, but sets a “moved” or “cancelled” flag and notifies the agency, when:
- the request has a client;
- the request has several artists — one artist’s calendar, Bandsintown or BIO doesn’t move a shared request;
- the request’s local date has passed or the performance is recorded;
- money has been received for the request;
- the request has several driving sources, or the link only observes.
The decision stays with the agency: change the date manually, decline the request, or leave it. See flags on a request. There’s no need to unlink the request from Bandsintown to move it: if sync doesn’t drive the request, the fields are open, and in a request with a client the agency changes the date, see locked fields.
Holds
Sync never releases holds. If an event is moved to a date with active holds or one taken by another request, the agency gets a separate warning.
Artist left, or agency unavailable
Sources don’t change requests of an agency the artist has left, or of a frozen agency.
More: Bandsintown, external calendar, BIO events.