Ooyala Flex 5.4.1 Release Notes 2017-02-22

Components/Updates required

  • Master
  • Publish
  • Transfer
  • Index
  • Job Nodes
  • Reviewer

Issues Fixed in 5.4.1


Expired review sessions are not displaying in the Expired carousel.

Resolution: This has now been fixed, and expired review sessions now appear in the Reviewer UI.


If users had multiple metadata instances, and they altered one of them, they were unable to identify which instance had been changed.

Resolution: To ensure that users are able to identify which one has been changed, we have added support for variable instance paths in the event data for metadata instances. From now on, the path of the instance will be displayed in the Event Details section for the metadata definition, instead of the name. This will make it easier to identify which metadata instance has been updated.

Storage Quotas

Users were unable to apply storage quotas per account. This was due to the fact that the Owner Name field had been removed from the storage item.

Resolution:  An Owner ID field has been added, so that each storage item stores the ID of the owner. From now on, when listing all of the quotas, it will show the quota usage per account.


The /assets/{assetId} endpoint was slow to return information for a specific asset.

Resolution: To solve this issue, we have changed the table hierarchy to joined-subclass as per flex-enterprise.

What’s New

Ability to Specify a Timeout in S3 Client

We have added support for request timeouts in the S3 resource. This is done using the following system property: “tv.nativ.mio.S3.client.timeout” You must set this property in seconds. If you do not specify a value, it will default to 600 seconds automatically.


Media Region Endpoint: the Media Region endpoint has been altered. Previously, it was known as “mediaRegion”. From 5.4.1, it will be known as “mediaRegions:”.

Stream Processor

We have created a basic integration of Ooyala Flex Stream Processor as a transcode resource, that supports transcoding based on named presets/configurations on the stream processor.


We have removed the redundant  executeScheduleJob() method, as scheduled event status updates are already being handled by the executeCreateFileActionJob() method.