Resolved after 2 days, on February 4, 2025.
Some print jobs replicated to the cloud node were taking longer than expected to process - Up to 2 minutes. This meant if jobs were released before the job was processed in the cloud AND the cloud node was required for successful job replication, then the job may fail. Our automated logging caught the problem and the cause was traced to a memory issue in the cloud node, causing it to restart, which has now been addressed. The issue is now resolved. The issue only occurred at peak times, and only effected small amounts of jobs.
Update timeline
- resolved Feb 25, 2025, 04:06 AM UTC
Some print jobs replicated to the cloud node were taking longer than expected to process - Up to 2 minutes. This meant if jobs were released before the job was processed in the cloud AND the cloud node was required for successful job replication, then the job may fail. Our automated logging caught the problem and the cause was traced to a memory issue in the cloud node, causing it to restart, which has now been addressed. The issue is now resolved. The issue only occurred at peak times, and only effected small amounts of jobs.
Your product runs on more than PaperCut
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services