Vista

DPK : batches stuck at RIP Complete status

Löst

Incident Resolved: CTIM-1936
Support Teams have contained or resolved the issue. Please contact MIS PBM or see ticket for more details.

Uppdaterad

UPDATE:

Teams continue to see marked improvement with errors dissipating dramatically over the last 10 minutes. However, a thorough check is required and so we have not Resolved this incident yet. Next update in max 30 minutes or once we can consider Resolved.

Uppdaterad

UPDATE:

We are seeing some improvement after recent containment attempt but due to heavy load this could take some time to reach various customers before we can confirm. Teams are working together at highest priority to resolve this. Next update in max 30 minutes.

Uppdaterad

UPDATE:

Teams have found likely culprits for the recent failures across artwork services which is causing incidents across all business units. Team has taken mitigation steps to resolve this and we are awaiting the results of those steps. Next update in max 30 minutes.

Uppdaterad

UPDATE:

Team continues to investigate at the highest priority the authorization issues currently affecting critical artwork services including Prepress which many service rely on. Next update in max 30 minutes.

Uppdaterad

UPDATE:

While the DPK IT team saw some improvement, the issue is not Resolved. Teams are now considering if this is related to a major Artwork services outage going on and being handled critically. We will provide updates on that investigation to see if it resolves this issue.

Uppdaterad

UPDATE:

Teams are currently trying to confirm if the incident is resolved but just experiencing residual latency post AWS outage/resolution. Next update max 30 minutes.

Utreder

New Incident: CTIM-1936
Plant: DPK
Priority: Critical
Escalation sent to: Fulfillment: Plant Optimizations/NPI for review.
Deer Park textiles workflow is down for approximately 2 hours now with items stuck in Schedule in the ‘RIP Complete’ Status which is blocking team from getting labels. There was an AWS outage, but post outage resolution (~25 minutes ago) the issue did not resolve. Please investigate.