Skip to main content

Newspapers Process - Production (DPG)

Alejandra M
Updated
  1. Summary
  2. Description
  3. Checks & Actions

Summary

DPG will release 73 newspaper titles, with an expected launch on May 1st (ZINIO side).

The subscription will act as middleware (similar to DPG magazines) and will be available on DPG platforms alongside newspapers and magazines:

Release schedule: Monday–Saturday (excluding Sundays and public holidays)  

Publication deadlines:

  • Weekdays (Monday to Friday): 6:00 AM CEST (9:30 AM IST)
  • Saturday: 7:00 AM CEST (10:30 AM IST)
    ⚠️ Reconfirm timings during CEST (daylight saving) changes.

Delivery window:
Files are typically delivered by DPG and updated between 8:00 PM – 1:00 AM CEST - 11:30 PM to 04:30 AM (IST). We receive the final files which are then ingested and should be processed by our system.

Description

Follow this process when any of the following issues occur:

  • File not delivered
  • File not ingested
  • File not published / display issues (OLR: unreadable text/images)
  • Not delivered to subscribers 

Checks & Actions

1. File Delivery Check

Timeframe: 4:00 AM (CEST) –7:30 AM (IST)

A) FILE NOT RECEIVED

Actions:

  • Check in slack channel DPG Newspapers Alerts if we get a notification showing: INTERNAL DPG issue is not receive or error processing, as per below: 

    • Use the 'Search in Channel' option, paste the below and hit Enter: 

      in:#dpg-newspapers-alerts "DPG issue not received or error processing" during:today


    • Make sure to review only the messages received on the day you are checking, starting from the beginning of that day.

 

  • Create BM Jira ticket "Issue Not delivered: Pub Name_Name of magazine_file name"

Notes: 

  • Same notification will be sent to DPG

  • If file is not received: Follow the process to contact DPG as per the next step in section C.

    As reference: The file comes with: (ISSUE DATE, PUBLICATION ID, PUBLICATION NAME)

    •  Eg.  15042026_45945 - Liemers - WDG_LI.xml

B) FILE RECEIVED BUT NOT PROCESSED BY FTP (INTERNAL ERROR) 

Below is an example of the error we see in the slack channel when an issue hasn't been received or was not processed:

Actions:

  • Check the file: pub id, publication name and issue date eg. 445964_Kampen-Flevoland-WST_FL_09-04-2026_20260325 

  • Verify in the slack channel DPG Newspapers Alerts if we received the message of issue received for that title: DPG issue received: name of the issue

    If received but not processed (ftp internal error): 

    • Raise Jira to Production (Assignee: Emilio)
    • Send Macro B2B::Troubleshooting::DPG - FTP Internal Error (Follow up with Production)/Subject: Production Alert: DPG - FTP Internal Error (Follow up with Production)

⚠️ Double check in slack channel we have received the file before sending email to Production Team.

Notes: 

  • Always ensure Ian or Ernest replies on the same channel/thread to give us the update of the problem 

  • Follow up every 30 min. if we don't get any updates

 

C) MISSING ISSUE

Timeframe: 5:00 AM (CEST) –8:30 AM (IST)

Actions:

  • Check in Slack DPG Newspapers Alerts if the missing issue has been delivered already (search for the file). It should show as: DPG Issue received: (PUB ID, PUBLICATION NAME, ISSUE DATE). As per below:

IF NO (delivered yet at 5:00 AM (CEST) –8:30 AM (IST) 

  • Send email to DPG 

    Only to be sent via your individual email (not via Zendesk) to DPG if the file has not received.
    Email servicedesk@persgroep.com  CC: brian.wolfkamp@persgroep.net and tijdschrift@navigaglobal.com
     

    Use macro: B2B::Troubleshooting::DPG - Missing Newspaper / Subject: [ZINIO] Missing Newspaper File Request contents to draft the email to DPG.

    IMPORTANT: Ensure the email tijdschrift@navigaglobal.com is in CC as it will create a Zendesk ticket to help us handle future communications regarding the issue with DPG. 

     

  • When file is received:  
    → Only send if we proactively contact DPG asking for the missing file 

    Use macro:  B2B::Troubleshooting::DPG - Missing Newspaper - File Received (Follow up with DPG) / Subject: [ZINIO] Missing Newspaper - File Received (Follow up with DPG)

IF YES (file received at 5:00 AM (CEST) –8:30 AM (IST) 

  • Send email to Production

           Email production@navigaglobal.com and on CC csall@navigaglobal.com

           → Use macro:  B2B::Troubleshooting::DPG - Missing Newspaper - File Received (Follow up with Production)/ Subject DPG - Missing Newspaper - File Received (Follow up with Production)

 

Timeframe: 5:30 AM (CEST) –09:00 AM (IST)

Actions: 

  • In slack channel DPG Newspapers Alerts check if the missing issue has been delivered
  • If Yes - Close BM Jira ticket created in section A

D) FILE RECEIVED

Actions:

  • Check via slack channel DPG Newspapers Alerts notifications are showing for each issue as per below (No further actions needed for Files received)

2. Ingestion Check

Timeframe: 4:30 AM CEST - 8:00 AM (IST) 

A) ISSUE NOT INGESTED

Actions: 

  • Check in Zendesk if we received an email Subject: (PRODUCTION) Ingestion failed for issue <NAME OF ISSUE>

Eg. Subject: (PRODUCTION) Ingestion failed for issue <747131>

Ingestion of XML newspaper-sequence-fail.zip & 3iFqWay3H7giWcca2qV1gvS1J3s1M failed

Issue id: 747131
Publication name: Mezza
Publication id: 38657

Ingestion is failing with the following errors: An error occurred while processing the ingestion for issue <747131>.

 

If YES

  • Double check in Admin Status shows as: Error

    • Go to Admin > Publications > Add Pub ID

    • Go to Issue details

If Status shows Error 

  • Raise Jira to Production (Assignee: Emilio)

  • Send Email to Production: Use Macro B2B::Troubleshooting::DPG - Ingestion Error (Follow up with Production)/Subject: Production Alert: DPG - Ingestion Error (Follow up with Production)

  • Post in #cs_production_issues. "Production Alert: Explanation of the Problem"

Notes: 

  • Always ensure Ian or Ernest replies on the same channel/thread to give us the update of the problem 

  • Follow up every 30 min. if we don't get any updates

B) ISSUE INGESTED

Actions:

  • Check via slack channel DPG Newspapers Alerts notifications are showing for each issue: DPG newspaper posted for ingestion. As per below:

 

Notes:

As reference, once ingested: The file comes now with ISSUE ID: (PUB ID, ISSUE ID, ISSUE NAME, ISSUE DATE)

DPG newspaper posted for ingestion: 45936_744194_28-04-2026_20260428.zip 

 

STATUS OF ISSUE IN ADMIN

READY: INGESTED

ERROR: ISSUE NOT INGESTED

LOCKED STATUS: ISSUE IS PROCESSING

PUBLISHED: ISSUE IS LIVE

3. Published Check (HTML Reader): Only for VIP Titles

Timeframe: Friday 6:05 AM CEST - 9:35 AM (IST)

Saturday 07:05 AM CEST - 10:35 AM (IST)

Actions:

  • Check VIP List
  • Go to the relevant publication page in admin from the 'Admin Link' added.
  • Check latest issue (verify the issue is released today)
    • Under 'Actions', click on 'Preview' to open the issue
    • Check a couple of pages, ensure the newspaper text and images loads correctly without error messages

If NO ERRORS were sent in ingestion and VIP titles are opening correctly

If ERRORS. The content is not displaying correctly not allowing the magazine to be read

  • Raise Jira to Production (Assignee: Emilio)
  • Send Email to Production: Use Macro B2B::Troubleshooting::DPG - Published Issues - Display Errors (Follow up with Production)/Subject: Production Alert: DPG - Published Issues - Display Errors (Follow up with Production)
  • Post in #cs_production_issues. "Production Alert: Explanation of the Problem"

Notes: 

  • Always ensure Ian or Ernest replies on the same channel/thread to give us the update of the problem 

  • Follow up every 30 min. if we don't get any updates

4. Delivery to Users

Timeframe: 6:30 AM CEST - 10:00 AM (IST) 

  • Check in Looker DPG Newspapers dashboard
    • Under Delayed Publish Date List, check all newsspapers have been published
    • Under Pending labels check no Labels are Pending

If there's a Delayed

If it's not a bank Holiday and the release date matches with today's day

If there are Labels Pending

  • 80% of the totals hasn't been delivered:
    → Raise Jira / Mayday with IT as per CS Managing a Mayday.

  • < 80% Raise a Jira and Post in P2 channel 

Newspapers impacted by this process

DPG Newspaper list.xlsx

Related articles