kpolsonslalom

[jolly cliff]

Hi 👋 no, the created field will not be updated when updates are made or an object changes state.

The guaranteed approach that is coming to mind, is to retrieve the object you want to check, compare it's contents with what you have stored, and update the information you have stored if it is different.

[glacial moss]

Alright, thank you for the information. A follow-up question, then--for payment intents in particular, is there any sort of time period after which they lock? E.g. if I were to ingest payment intents for the last 7 days would that be enough to identify any objects that may have updated?

[jolly cliff]

I don't think that would be a good approach, Payment Intents do have some terminal states (such as succeeded and canceled), but they can stay in an intermediary state indefinitely.

[glacial moss]

Could consuming events lead to the desired outcome?

[jolly cliff]

Maybe, what is your overall desired outcome?

[glacial moss]

e.g. pull events of type payment_intent.*

Ultimately we are looking to pull everything into a data warehouse to enable analytics

So we need to be able to identify if an entity has changed

Otherwise our data will become stale

Also to note, unfortunately the Data Pipeline product is not an option as we are not working in the AWS ecosystem

[jolly cliff]

That's exactly what I was looking for the documentation for. Not in Snowflake either?

[glacial moss]

Unfortunately no

BigQuery

[jolly cliff]

My fear with relying on Events, is that there is no payment_intent.updated event for little things like changing the amount, for those objects in particular there are only Events that correspond with the intent changing states.