How to Find and Sync Media in FanvueAutomation Vaults

Find the file before changing the workflow

A missing item in Vaults can mean several different things: the wrong creator account is selected, filters hide the file, the current page does not contain it, or the library needs attention. Uploading the same file again is not the first diagnostic step.

This guide separates browsing, synchronisation and local uploads. It explains what to check without assuming that a visible thumbnail proves a file can be delivered by every automation workflow.

Start with the account and a broad view

1. Open Vaults and select the intended creator account. Check the account name and username, especially when you manage several creators.
2. Set Folder to All folders and Type to All types.
3. Clear Search media. Review the unfiltered list before deciding an item is missing.
4. Use the page controls to inspect additional results. The first page is not the whole library.

Changing account resets the folder, type and search filters. Changing a filter returns the view to page one. Keep the selected account in mind throughout troubleshooting rather than comparing counts from different creators.

Narrow the search one condition at a time

The search field is labelled Title, filename, or AI description. Try a distinctive word from the file's title or description, then narrow by image or video and by folder. If that produces no results, remove one condition at a time.

For example, imagine a fictional item titled “Blue studio introduction”. Search for “studio” with All types selected before adding a folder filter. This is a manually written search example, not a customer file or an observed test result.

A useful title and factual description make later selection easier. Describe what the file actually contains; do not add an invented price, delivery promise or misleading description to compensate for missing configuration elsewhere.

Know what Sync is for

Sync requests a refresh from the connected Fanvue vault into FanvueAutomation. The ordinary button requests an incremental sync, not an unconditional full rebuild. Folder information is cached; opening the folder selector alone is not a fresh synchronisation.

On an account you are authorised to manage, choose Sync deliberately and wait for the result. The button shows Syncing... while that request is pending. Read the success or error message, then check the specific item you need.

A completion message and a synced-item count do not establish that every remote file was imported or that an attachment will send successfully. Individual items can encounter errors, and an incremental refresh is not the same as rechecking the entire historical library. This guide does not promise a refresh interval or a completion time.

If the application says the account is not connected, address that connection before repeating Sync. If the same error continues, record the time and exact error for support rather than repeatedly uploading duplicate files.

A local upload is not a Fanvue upload

Upload Media stores a file in the selected account's FanvueAutomation vault. In the verified implementation, that upload is marked local-only; it does not upload the file to Fanvue. The Sync described above brings information from Fanvue into the application, not the other way around.

Do not interpret a successful local upload as confirmation that the file is present in Fanvue's own vault. Check the intended destination separately. Likewise, seeing an item in Vaults is not proof that a Script or PPV product already references it correctly.

Use a short troubleshooting record

• Account: which creator is selected?
• View: which folder, type, search term and page are active?
• Origin: was the file uploaded locally or is it expected from Fanvue?
• Refresh: when did you request Sync, and what exact result did it show?
• Expected item: can you identify its approved title or filename without sharing private fan information?

If the file appears after clearing filters, the problem was visibility in that view, not evidence of a failed upload. If the file is visible but a later workflow fails, preserve that distinction when asking for help. Do not delete or recreate working content simply to make the list look different.

Review before using content in automation

Check that the selected file belongs to the intended creator and accurately matches its title and description. Review the relevant Script or PPV configuration separately, then use an authorised test workspace for the workflow. Do not test deliveries against real fan conversations for a marketing demonstration.

Our Playground guide explains fictional-message testing. A read-only staging tour does not perform a real generation or delivery test. Content organisation is preparation, not a sales guarantee.

Scope of this guide

The Vaults interface source, API and sync-service implementation were checked on 19 September 2026. This is source-verified guidance, not a recorded end-to-end sync or delivery test. No account settings, files or private fan conversations were changed to prepare it.

FanvueAutomation is an independent third-party tool, not affiliated with or endorsed by Fanvue.