#ayesha-shaikh_api

1 messages · Page 1 of 1 (latest)

rapid tendonBOT
candid heronBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

rapid tendonBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1253250504499265621

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

echo glacier
#

Hi,

No, there is not.

sonic geode
#

since all these updates are under same event, only way to see updated fields is previous_attributes?

echo glacier
#

Yes, that is correct

sonic geode
#

and is there any list of all possible updates

echo glacier
sonic geode
#

i meant for this event, customer.source.updated - what are all possible updates?

echo glacier
#

That occurs when a source’s details are changed. There is not a list of all updates I can share with you.

sonic geode
#

okay, thanks