When a delivery doesn't finish
A delivery of configuration can land most of what it carried and still hold a few items back. Here's how to read what happened, and what to do about each kind of hold-up.
A delivery updates each configuration item in turn. It works out an order that puts everything an item needs ahead of the item itself. Most of the time everything goes through. Sometimes a few items don't, and the delivery tells you which ones and why.
Partly done is a normal outcome
Mochi reports what actually happened: “Mostly done”, with “17 of 19 items updated” beside it, rather than a single pass-or-fail verdict. The items that went through are genuinely in that environment. Open the delivery to see every item and what happened to it.
An item is waiting on something
Most hold-ups are about something an item points at. There are three of them, and the fix is different each time, so read which one it says.
- “Waiting on something in this delivery that didn't go through.” Something further up the list didn't make it, and this item needs it. Sort that one out and this one follows on the next run. There's nothing to do about this item itself.
- “Needs something that isn't in this delivery.” The item points at a field, group or category that the target environment doesn't have and this change set doesn't bring. Mochi names it. Add it to a change set and send it along.
- “Points at something that no longer exists.” The item refers to something that isn't in the environment you're moving it from either. That's a broken reference. Nothing about this delivery can fix that; repair it where the configuration lives, then move it.
Some settings can't change once an item exists
A few things about an item are fixed the moment it's created: a field's type, how it handles languages, and where it applies. If one of those differs between environments, the only way to make them match would be to remove the item and build it again, which would take everything already stored in it with it.
Mochi won't do that on its own. It stops, names the one setting that can't change, and leaves the decision to you. Either make that change directly in the target environment, or remove and re-add the item deliberately.
Some things the environment won't allow
Not every hold-up is about your configuration. An environment can refuse an item on its own terms, and Mochi passes on what it said. The usual ones:
- The environment's credentials need more permission. User groups in particular ask for more than a configuration account usually carries. Give that account the permission it needs, or create those items in the environment directly.
- The item belongs to a built-in feature. Some fields come with an Aprimo feature and are looked after by it. Mochi is happiest leaving those alone, so they're worth stopping tracking and they won't come up again.
- A name or identifier is already taken. Some values have to be unique within an environment. If something else there already uses it, the delivery stops rather than pick one for you.
Calling a delivery off
A delivery waiting to be approved holds its environment until someone acts on it, so nothing else can be sent there in the meantime. If it was started by mistake, or it's waiting on someone who isn't going to get to it, choose Call it off. Nothing has been sent yet, so nothing is undone. It just frees the environment up. You'll be asked why, and that stays on the history.