Issue Opening PDF, Markdown, and Custom Components in Multimodal Project
major- Started
- May 7, 3:30 AM EDT
- Resolved
- May 7, 5:09 AM EDT
- Duration
- 1h 39m
SuperAnnotate's updates (5)
- investigating · May 7, 3:30 AM EDT
We’re currently experiencing issues opening items with PDF, Markdown, and some custom components in the Multimodal project. We’re investigating the problem and working on a fix.
- identified · May 7, 3:45 AM EDT
The issue has been identified and fix is being implemented.
- identified · May 7, 5:09 AM EDT
We are continuing to work on a fix for this issue.
- resolved · May 7, 5:09 AM EDT
The issue is confirmed to be resolved.
- postmortem · May 7, 6:24 AM EDT
During the recent release, an issue occurred in the CDN distribution that serves external frontend libraries. As a result, requests to load certain static assets \(e.g., `pdfjs-express/8.7.2/webviewer.min.js`\) returned `504 Gateway Timeout` errors. Because several components \(PDF, Markdown and other custom components\) depend on externally hosted CDN assets at runtime, the failure to load these scripts caused those components from initializing or functioning correctly. The root-cause was not related to component logic itself, but by the unavailability of required CDN resources during application initialization.
Updates are SuperAnnotate's own words from its status page (status: postmortem); we never add an inferred cause. The vendor's incident page ↗