Mimir integration – Admin monitoring & error handling

Integration guard

To protect stability, an integration guard will automatically pause the integration per tenant when:

repeated authentication or permission errors occur

Symptoms

Custom actions immediately fail with an explanatory message.

Resolution

Fix the underlying issue (API keys, permissions).
Update the integration via the admin API.
On a successful update, the integration guard for that tenant is cleared and processing can resume.

Common scenarios

Scenario	What you see	What it usually means	What to do
Validation error on processing appraisal	400 error + descriptive comment on item	Invalid or inconsistent processing configuration (or not supported for the chosen item)	Fix the configuration or try a different item
“Too many processings for this source” comment	No new job, but a comment on the item	`maxAllowedProcessingsPerPixopSourceVideo` limit exceeded	Review processing usage and config; raise the limit if appropriate
“Processing conflict / insufficient funds” comment	Job not started, comment explains cost issue	Account does not have enough credits or processing cost changed	Add credits (by contacting api@pixop.com) / adjust configuration, then retry
Custom notification failure	Email notification instead of Mimir notification	The Mimir integration user lacks the `Tenant administrator` permission	Add the missing permission
Ingest fails due to invalid or inaccessible Mimir HighRes URL	400 error from Pixop with an error indicating the ingest could not fetch partial content (expected `206`) and that the remote URL responded with `403` or `404`	The HighRes download URL provided by Mimir is expired, missing, blocked by permissions, or otherwise not reachable by Pixop	See “HighRes URL invalid or inaccessible” below
Cannot delete Pixop master video (processed videos not transferred)	Pixop Integration Notification stating the master video cannot be deleted because processed Pixop videos are not yet transferred to Mimir	One or more processed Pixop videos belong to a Mimir master video but were not transferred back to Mimir (often because processing was started directly in the Pixop web app, not from Mimir)	Handle the processed videos manually (download/upload to Mimir if needed), delete the processed videos in Pixop, then retry deleting the master video
500 errors from integration	“Internal server error” with generic message	Unexpected exception in integration	Please report the issue to api@pixop.com

HighRes URL invalid or inaccessible (403/404)

During ingest, Pixop downloads media from Mimir using the item’s HighRes URL. Pixop performs a ranged (partial) download, so it expects the URL to support HTTP range requests and respond with 206 Partial Content.

If the HighRes URL is missing, expired, or access-controlled, Pixop may receive:

404 Not Found (the URL no longer exists, or points to a removed/invalid resource), or
403 Forbidden (Pixop is not allowed to access the URL — e.g. permissions or token expired).

In these cases, ingest fails and you may see an error similar to:

Partial content not received. Expected status code: 206, received status code: 403

What to check

Verify the HighRes URL is valid
- Open the item in Mimir and confirm the HighRes media is available.
- If the URL is time-limited, regenerate it (or retry ingest from Mimir so a fresh URL is used).
Verify permissions/access
- Ensure the media is accessible to the Mimir user/context that generates the URL.
- If your environment uses restrictive network rules, ensure Pixop can reach the HighRes URL.
Verify range support
- The HighRes endpoint must support HTTP range requests and return 206 Partial Content for ranged downloads.
- If the endpoint always returns 200 OK (full content) or blocks ranges, ingest may fail.

How to recover

Retry Ingest in Pixop once the item’s HighRes URL is confirmed valid and accessible.
If the issue persists across multiple items, contact api@pixop.com and include the details of the Pixop Integration Notifications.

Cannot delete Pixop master video because processed videos are not transferred to Mimir

What you see

A Pixop Integration Notification similar to:

Cannot delete Pixop master video with Pixop ID: <PIXOP_MASTER_VIDEO_ID> because the following processed Pixop videos are not yet transferred to Mimir. Please handle them manually and delete them afterwards from Pixop to allow deletion of the master video:
[PixopID: <PIXOP_PROCESSED_VIDEO_ID> MimirID: <MIMIR_ITEM_ID>]

What it usually means

To avoid automatically deleting paid processing results, the integration only deletes a Pixop master video when it can confirm that all processed Pixop videos belonging to that master have been transferred back to Mimir.

A common cause is that processing was started directly in the Pixop web app on a master video that originates from Mimir (instead of being triggered from Mimir via custom actions). In that case, the integration cannot transfer the processed result back to Mimir automatically, so the master video is not eligible for automatic deletion.

What to do

Decide whether you need the processed video
- If yes: download the processed video from Pixop and upload it manually to Mimir.
Delete the processed Pixop video(s) manually in Pixop
- In the Pixop web app, open the processed video, click ... and choose Delete.
Retry deleting the master video
- Once the blocking processed videos have been handled and deleted in Pixop, the master video can be deleted.

If you need help identifying which videos to delete, use the Pixop IDs and Mimir item IDs listed in the notification.