Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Issue with cached old field (in meanwhile changed in the table) into the connector 'filterClause'

We have a scheduled integration that retrieves records from BigQuery daily. After processing the data, we send it to Salesforce. Since we have a large number of records, we implemented pagination using a "While Loop". In each iteration, we process 25 records, iterating through them with a "For Each" loop to create records in Salesforce.
Everything was working as expected, but an issue has occurred (see the explanation below):


After changing the field (updated_at -> updated_at_berlintz) in the table (BigQuery), the integration application stopped working.
We made all the necessary changes to the integration, and now it works for the first iteration (sometimes first few) but fails on the second (or third/fourth). 
In both cases “filterClause” is the same, E.g. :

updated_at_berlintz >= ‘2025-03-26 18:00:00.000 UTC’ AND updated_at_berlintz <= ‘2025-03-26 23:59:59.999 UTC’

But somehow it works only at the begining (first few iterations) and after that we have following error message:

{ “message”: “{\“error\“:{\“code\“:400,\“details\“:[{\“@type\“:\“
type.googleapis.com/google.rpc.ErrorInfo\“,\“metadata\“:{\“cause\“:\“[400] Name updated_at not found inside prod_export.salesforce_orders_items at [1:708]. \“,\“conditions\“:\“updated_at_berlintz >= ‘2025-03-26 18:00:00.000 UTC’ AND updated_at_berlintz <= ‘2025-03-26 23:59:59.999 UTC’\“,\“connection_type\“:\“Bigquery\“,\“entity_type\“:\“prod_export.salesforce_orders_items\“}}],\“message\“:\“Unable to list entities.\“,\“status\“:\“FAILED_PRECONDITION\“}}“, “code”: 500 }

dejancvetkoski_0-1743198793704.pngdejancvetkoski_1-1743198865018.png

dejancvetkoski_2-1743198915793.png

 



What could be the issue? It looks really strange. I appreciate every help, thanks in advance!

2 REPLIES 2

Hello @dejancvetkoski,

We saw your question and wanted to let you know we’re keeping it on our radar. We’ll also invite others in the community to pitch in and share their thoughts.

Hi @dejancvetkoski, after updating the big query field, did you try to "Refresh Connection Schema"? Is the issue still persisting?

 

shagufthazk_1-1745402657735.png

 

Top Solution Authors