Your first video workflow.

Request an evaluation before assuming a particular route is open. Existing users can log in and select a visible project. A login account alone does not establish access to every capability.

In the workspace, open Media and add material you have the right to process. Keep the browser available while uploading; interrupted uploads may be resumed when their session and source are still valid.

Wait for the media asset to become ready before creating a task. A completed transfer is not necessarily completed media preparation.

Create a task from ready media. Use only the mode and source/target language pair offered by the current workspace. If the route you need is absent, do not substitute another language or assume the service can process it.

Check the product and capability boundaries or review an evaluation scenario.

Task pages show queue, processing and terminal states. Refreshing reads service state; an accepted request is not a completed output.

When a result is available, inspect its read-only preview and download the listed artifacts. SRT and VTT are subtitle formats; an available subtitle file is not a rendered or dubbed video.

If preparation or processing fails, inspect the displayed reason and use retry only when the service offers it. Cancellation and retry availability depend on task state. If a download link expires, request a fresh download through the workspace.

When contacting support, describe the stage and visible error without sending tokens, signed URLs, media contents or provider responses.

Review retention, deletion and access boundaries. Server-side integrations should use the candidate public API guidance, not internal processing or storage access.