Adilo caption backfill

Caption backfill imports available Adilo subtitles and translations for videos that were already imported into Playflow. It does not reimport media, create another video, or replace the original import job.

Availability and eligibility

Adilo integration is available on Fleet. A workspace owner or admin must have an active Adilo connection. A video is eligible only when it has a successful Adilo import record, an Adilo file ID, and the credential fingerprint of the current connection. Reconnecting a different Adilo account can make earlier imports ineligible.

Run from workspace settings

In the Adilo integration panel, choose Bring over captions. The app works through eligible videos in batches of four and aggregates imported, unavailable, and failed counts. One run stops after 1,000 videos. Run it again to continue if the workspace has more eligible items.

The app skips items already marked captions_imported during automatic paging. A selected-video API request can explicitly check one to four imported videos.

Result meanings

• Imported: at least one language was stored. The result lists those languages. A partial result can also report translation errors.
• Unavailable: Adilo returned missing video or caption data, or no caption data was available.
• Failed: no language could be stored because of authentication, access, rate, provider, validation, or other request failures.

Every checked video receives an integration audit entry. A failed caption operation does not change the successful media-import status and does not delete the video.

Existing captions and partial languages

Each available Adilo subtitle or translation is handled as its own language track. Missing data for one language does not stop another language from importing. Playflow uses the current transcript version when writing a language and never deletes an existing track as part of backfill. Review per-language errors when a result reports partial success.

API selection and paging

Call POST /api/integrations/adilo/captions/backfill. Send one of the following request bodies:

• {"videoIds":["uuid"]} with one to four unique Playflow video UUIDs.
• {"cursor":"uuid"} with the prior response's nextCursor.
• {} to start automatic paging from the beginning.

videoIds and cursor are mutually exclusive. A response contains total, imported, unavailable, failed, nextCursor, and items. Each item contains its video ID, title, status, imported languages, errors, and nullable reason. Continue with nextCursor until it is null.

Retry guidance

Unavailable and failed items do not block the remaining batch. Correct expired credentials or provider access first, then run backfill again. The provider work has a bounded request window, so large libraries must be paged rather than treated as one long request.