Verify your assets in MK.IO

After creating, importing, or running an encoding job on an asset, verify that MK.IO has correctly indexed the content before publishing. This helps you catch storage configuration issues or encoding errors early.

What to check

On the asset page, scroll down to see two key sections:

• Tracks — Shows the video, audio, and subtitle tracks MK.IO has detected in the asset’s files. After a successful encoding job, you see entries for each resolution, audio track, and any included subtitles. If this section is empty after encoding, something went wrong.
• Files on storage — Lists every file in the asset’s cloud storage container, along with file size and last-modified date. This updates as files are added or generated.

Steps

Open the asset

Go to Assets and click the asset name you want to verify.

Check Tracks

Scroll to the Tracks section. After an encoding job completes, you should see rows for each video track (labelled by resolution), each audio track, and any subtitle tracks.

Check Files on storage

Select the Files on storage tab. You should see the source files you uploaded plus any output files generated by encoding — including .ism manifest files, encoded video chunks, and log files.

Troubleshooting

No tracks appear after an encoding job

The encoding job may have failed. Go to Video Processing > Jobs and check the status of the job. If it shows Error, open the output asset and check the highlevel.log file in Files on storage — this file contains diagnostic details you can share with MK.IO support.

Files on storage is empty

Your cloud storage may not be connected correctly, or the asset was created pointing to an empty container.

• Confirm your storage account is still connected and credentials have not expired. Go to Storage in the left navigation and check the status. For help reconnecting, see Connect cloud storage.
• Check that the container name in the asset matches an actual container in your cloud storage.

Files appear but Tracks section is empty

MK.IO detects tracks from encoded output files (manifest + encoded segments). If you see only a raw source file (for example, source.mp4) with no .ism file, the asset has not been encoded yet. Run an encoding job first. See Configure VOD transforms.

Asset looks correct but content does not play

Tracks and files being present means the content is stored and indexed correctly. Playback also requires a streaming endpoint and streaming locator. See Publish content for streaming.

If you have checked the above and still cannot see your assets, visit the MK.IO support portal for further help.