API ReferenceChangelog
Log In
Changelog
Improved

v1.0.0-rc.6 – Mimir Integration Enhancements and API Improvements

v1.0.0-rc.6 – Mimir Integration Enhancements and API Improvements

Date: 2025-11-12
Status: Release Candidate 6

This release includes extensive improvements identified during continued work on the Pixop–Mimir integration, along with API bug fixes and internal enhancements.

Internal

  • Introduced new alerting and integration utility components:
    • AlertNotifier and SlackAlerts for improved visibility and error notifications

Pixop API

Fixed

  • Resolved an issue where filtering videos by masterVideoId on the /videos endpoint could result in a 500 error

Added

  • New optional videoDescription parameter for all video processing endpoints that start a job
  • New videos/{videoId}/compare-with/{targetVideoId} endpoint added, along with two new related ErrorCodeEnum values
  • Added videoId field to the SourceVideo schema

Mimir Integration

  • Combined the two custom actions for accepting and rejecting processing jobs into one, now with a confirmation step to select the action
  • Combined the two custom actions for deleting with or without derived videos into one, also with a confirmation step
  • Replaced multiple custom actions for requesting processing jobs with a single unified action, where the desired processing configuration is selected in a confirmation step
  • Now assigns comments on items to notify Mimir users about completed or failed processing jobs
  • Stores information in Pixop when data has been saved in Mimir to determine when a master video can safely be deleted
  • If both master and processed videos are fully ingested, a comparisonLink is now added to the Mimir item to easily compare source and processed videos
  • Introduced an integration guard to automatically pause integrations per tenantId when repeated authentication or permission errors occur
  • Integration guard pauses are automatically cleared after a successful integration update via the admin API
  • All custom actions now first check the integration guard state before proceeding
  • If a Mimir custom notification fails, it now falls back to email delivery
  • Added a new configuration option maxAllowedProcessingsPerPixopSourceVideo to help control processing costs
  • The pixopUserId associated with the Pixop API key is now included in log statements for better traceability
  • Approval jobs older than one day are now automatically removed
  • Added a JMX endpoint for manually pausing or unpausing a tenant by ID
  • Improved exception handling and alerting for more robust operations
  • When an ingestion job already exists in Pixop for a Mimir item, the existing videoId is returned instead of creating a duplicate
  • When an equivalent processing job already exists or the configured processing limit per source is reached, a comment is added on the Mimir item instead of starting a new job
  • Permissions to update a Mimir item are now verified before creating a new version to prevent uncompletable processing workflows
  • PixopProcessingConflict (e.g. due to insufficient funds or changed processing cost) now results in a descriptive comment on the Mimir item
  • Improved handling of potential failure scenarios to reduce unhandled exceptions
  • Metadata updates from the integration no longer overwrite the item’s existing formId with the default
  • Old versions of custom actions are now deleted selectively based on URL ownership, allowing local/staging versions to coexist with production versions
  • When setting up a Mimir integration, two user groups are now automatically created if missing:
    • pixopIntegration (no permissions; controls who can access the custom actions and read the metadata created by the integration)
    • pixopIntegrationApiUser (granted the permissions needed for Mimir API calls)
  • Deleting a video now ignores derived clips, ensuring the master video can still be removed
  • Video searches in Pixop are now filtered by both pixopTeamId and defaultProjectId
  • Default daysToLive for integrations is now 90 days and is automatically extended when new jobs are created

Notes

  • This release strengthens the stability and observability of the Pixop–Mimir integration ahead of the stable v1.0.0
  • Please report feedback or issues to [email protected]