Delivery error: PGS-220000 PostgreSQL error: ERROR: relation ‘wkdlv_********’does not exist | Community
Skip to main content
Level 2
May 29, 2025
Solved

Delivery error: PGS-220000 PostgreSQL error: ERROR: relation ‘wkdlv_********’does not exist

  • May 29, 2025
  • 1 reply
  • 511 views

We are getting this error when we are linking the data from an excel file using data loading. We even faced this when the data was stored in a List in ACC and linked the list. We tried restarting workflow, adding an enrichment before delivery or/ and after linking enrichment. But same error. Temporarily we are using a work around of string the final data into a list and then using that list to send out the deliveries. 

 

Any way to solve this issue other that the work around I mentioned above.
Below is the screenshot of the error.



Here is the text version:


05/29/2025 9:14:55 AM PGS-220000 PostgreSQL error: ERROR: relation "wkf593291937_491_1_all" does not exist LINE 1: ...taId FROM wkf593291937_476_1 AS Ext_W0 INNER JOIN wkf5932919... ^ SQLState: 42P01.
05/29/2025 9:14:55 AM WDB-200001 SQL statement 'INSERT INTO wkf593291937_491_2_ALL(iLineNum,sCountry,sMarketing_Name,iProductId,sFlavor_Name,sPLU,sProduct_Description,sProductName,iTargetDataId ) SELECT Ext_W0.iLineNum,Ext_W0.sCountry,Ext_W0.sMarketing_Name,Ext_W0.iProductId,
05/29/2025 9:14:55 AM Ext_W0.sFlavor_Name,Ext_W0.sPLU,Ext_W0.sProduct_Description,Ext_W0.sProductName,Src_W0.iTargetDataId FROM wkf593291937_476_1 AS Ext_W0 INNER JOIN wkf593291937_491_1_ALL Src_W0 ON (Ext_W0.iProductId=Src_W0.iMost_purchased_menu_item_id)' could not be execu
05/29/2025 9:14:55 AM ted.

 

Best answer by Jayeshb

We found the solution for this. 

 

This is a V8 ACC instance. The targeting data and the data from the data loading activity both were from different data source. Using Change data source activity we changed the data source for data loading flow to match data source of targeting data flow and the issue was solved. 

1 reply

JayeshbAuthorAccepted solution
Level 2
May 29, 2025

We found the solution for this. 

 

This is a V8 ACC instance. The targeting data and the data from the data loading activity both were from different data source. Using Change data source activity we changed the data source for data loading flow to match data source of targeting data flow and the issue was solved.