# Delivery to Vendor Service

{% hint style="warning" %}

#### Note that service has been replaced by the [Make Delivery](/artist-anywhere/i-o-tools/make-delivery.md) tool.  <a href="#h_01jqa69xbf4x18a6rhsr6wpcdd" id="h_01jqa69xbf4x18a6rhsr6wpcdd"></a>

#### The service still works so the documentation is being maintained for those who prefer it. <a href="#h_01jqa69xbf4x18a6rhsr6wpcdd" id="h_01jqa69xbf4x18a6rhsr6wpcdd"></a>

{% endhint %}

## Details <a href="#h_01he6hxy4qyhk0tx1j8nbmrgh5" id="h_01he6hxy4qyhk0tx1j8nbmrgh5"></a>

The Delivery to Vendor Service is a custom feature of Artist Anywhere. Through using the Artist Anywhere Studio Workflows Tools, files are already in the the Artist Anywhere Cloud, and there is no need to upload the files before transferring them to a Vendor. Even a large number of files will transfer very quickly, as AWS can handle copying thousands of files in parallel.

You run the Delivery to Vendor Service through an automation within ShotGrid.

## Initial Setup <a href="#h_01he6hxd67qpq90zk2sszdtcew" id="h_01he6hxd67qpq90zk2sszdtcew"></a>

For the Vendor to Delivery service to work with your files, there are some setup requirements:

* All files you wish to send must be linked to **Versions** in ShotGrid as Published Files.
* All files must have been ingested onto an Artist Anywhere server and uploaded to our **Artist Anywhere Cloud**. When the Ingest Queue(link) ingests files, it queues them for upload to the **Artist Anywhere Cloud** and they will be uploaded as fast as the connection allows. Files will likely be available a few minutes after ingest, but depending on volume, they may take longer. &#x20;
* The recipient must be a Group with a Vendor Bucket specified in the **Vendor Remote Folder** Field in ShotGrid. <br>

  <figure><img src="/files/lgWJ8YpRj2T2LfSoAIIh" alt=""><figcaption></figcaption></figure>

## User Interface and Workflow <a href="#h_01he6hysejybhvq3z25qh0ccbj" id="h_01he6hysejybhvq3z25qh0ccbj"></a>

### Prepare Delivery <a href="#h_01he6hxd675ae3ntb34ejhrrnx" id="h_01he6hxd675ae3ntb34ejhrrnx"></a>

In order to send files, you must first **link the files you wish to send to a Delivery record in ShotGrid**.

{% hint style="success" %}
To send only the EXR files in a Delivery, include **\_EXR**, **\_EXRS**, **\_exr**, or **\_exrs** at the end of the Delivery’s name, for example **DeliveryToVendor\_EXR** or **final\_delivery\_exrs**.
{% endhint %}

### The Playlist to Delivery App <a href="#h_01he6hxd67er2acb1zkqn483ce" id="h_01he6hxd67er2acb1zkqn483ce"></a>

**We strongly suggest using the** [**Playlist to Delivery**](/artist-anywhere/i-o-tools/playlist-to-delivery.md) **app to create your Delivery.** This tool takes a Playlist and converts it to a Delivery that is ready to send to a Vendor.

### Manual Delivery Creation <a href="#h_01he6hxd67d4xwyj2wk6nkmam8" id="h_01he6hxd67d4xwyj2wk6nkmam8"></a>

Alternatively, you can create the Delivery record in ShotGrid manually and populate its **Versions** field with the Versions associated with the files you wish to deliver.&#x20;

You can specify Versions at Delivery record creation time:&#x20;

<div align="left"><figure><img src="/files/wrMNG100PcmfXaBUjrv2" alt="" width="563"><figcaption></figcaption></figure></div>

You can also add Versions to an existing Delivery record:&#x20;

<figure><img src="/files/fzAHZl01Nn4vdD6rovft" alt=""><figcaption></figcaption></figure>

### Sending a Delivery <a href="#h_01he6hxd672vkd42pncgj8v2es" id="h_01he6hxd672vkd42pncgj8v2es"></a>

Once you’ve set up your Delivery record, you’ll need to set a few values on it, then it will be ready to send.

First, make sure your Delivery record’s **Type** field is set to **Delivery** or **Delivery to Vendor** (depending on setup) and the **Delivery Method** field is set to **Cyclone**. We recommend additionally filling in the **Description** field with any information the recipient needs to know.

<figure><img src="/files/ZEcVzDKD1lY4b4IIBOZf" alt=""><figcaption></figcaption></figure>

Next, make sure the **To** and **From** fields are filled in correctly.

<figure><img src="/files/0ZtMZDjcT4bagb8FEIx8" alt=""><figcaption></figcaption></figure>

Set the Delivery’s Status field to **Automate!**

<figure><img src="/files/8rL76HIaW3vBGGAOcsmN" alt=""><figcaption></figcaption></figure>

Do a final review to make sure all your data is correct and your Versions are exactly what you want to send.

Finally, click the **Cyclone Deliver** checkbox. This will trigger the automated delivery service.

<figure><img src="/files/Jjb1yezf48266huGkvXH" alt=""><figcaption></figcaption></figure>

The process will start, the Delivery’s **Status** field will update with changes, and when the delivery service has completed, it will set the **Status** field to **Received**, meaning that the Vendor has received your Delivery successfully.

## Troubleshooting <a href="#h_01he6jfgxana5a6sz8ss1w8phx" id="h_01he6jfgxana5a6sz8ss1w8phx"></a>

If you follow the troubleshooting steps below and are still experiencing issues, please reach out to us at <support@artistanywhere.io>.

### Sending to Vendor <a href="#h_01he6hxd6708sx7qmakff66m36" id="h_01he6hxd6708sx7qmakff66m36"></a>

**Artist Anywhere** uses a unique identifier called a **GUUID** to track files throughout the transfer process. GUUIDs are generated as part of the ingest process, and most issues when sending arise because GUUIDs haven’t been generated yet.&#x20;

To confirm that files have GUIIDs, in ShotGrid, go to the Detail Page of the **Version** the files are linked to and navigate to the **Published Files** tab. There, you can check the **GUUID Status** field on each Published File. If any of those do not show **OK**, then GUUIDs have not been generated for those files, and you will be unable to send them.

<figure><img src="/files/VDNTcn9QTNaxgzM53yI3" alt=""><figcaption></figcaption></figure>

There are a few possible reasons and fixes for this:

* The files were very recently ingested, and the GUUID generation portion of the ingest process has not completed yet. This can take a few minutes after ingest to complete. Wait a few minutes and try again.
* AWS or ShotGrid was under maintenance or experiencing an outage. If an ingest occurs under those conditions, Artist Anywhere *should* go back and generate any missing GUUIDs. But if it hasn’t done so, right-click on any **Versions** that do not have a GUUID and select **Update GUUIDs** from the resulting context menu. They should generate within a few minutes of running the tool.

<div align="left"><figure><img src="/files/SbrMSg1FxJfH4qPUtdK0" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
You’ll need to be logged into ShotGrid Desktop in order for the **Update GUUIDs** menu item to show up.
{% endhint %}

* There is a path issue, most often caused by **capitalization problems**.Windows and Mac do not treat "A" and "a" as different letters, but the Artist Anywhere tools do. So, if an expected folder path is **previz** but someone has manually created a folder named **Previz**, the file will ingest but the GUUID will not generate. Ensure that there are no character case mismatches between paths in ShotGrid and on disk and try again.
* **File count mismatch:** When sending EXRs, if the number of files found does not match the expected number of files, an error will be generated. For EXR sequences, you can look at the **GUUID Name** field on the Published File to troubleshoot GUUID issues for individual frames and get more information by clicking on individual GUUIDs. If there is a discrepancy between the number of items in this field and the number of frames in the EXR sequence, then this is the source of the problem. If there are duplicate GUUIDs, you can delete the duplicates. If there are missing GUUIDs, then you’ll need to reingest the sequence.  If this is a duplicated published frame, you can delete it on the GUUID’s detail page. If a frame is missing, you will need to reingest the Submission.

### Vendor Receiving <a href="#h_01he6jjwm9gecc7yps0qtvtg24" id="h_01he6jjwm9gecc7yps0qtvtg24"></a>

Vendors receive files from Artist Anywhere via their **Vendor Bucket in AWS**. They receive the following when we onboard them to Artist Anywhere:

1. The instructions for downloading a the third-party tool needed to access their Vendor Bucket
2. The Keys needed to pull files from the Bucket

They may experience issues with either the keys or bucket access.&#x20;

* **Key issues:** If the Vendor cannot access or download from the Bucket, please have them reach out to us at <support@artistanywhere.io> to confirm their keys are active.&#x20;
* **Bucket access issues:** It is not uncommon for Vendors, who have strict security requirements, to have firewall rules that can prevent accessing their bucket. If a Vendor mentions that they get **Server not found** or a similarly worded error when trying to access the Bucket, that means either they have the bucket name wrong or their firewall is blocking access. Please have them confirm the Bucket name (generally **productionname-vendorname**) and make sure they have opened their firewall to reach the Bucket via https at **s3.amazonaws.com/bucketname**.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://artist-anywhere.gitbook.io/artist-anywhere/i-o-tools/delivery-to-vendor-service.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.