#yi_unexpected

1 messages ¡ Page 1 of 1 (latest)

sand questBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1402889971358240779

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

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.

graceful plover
#

Hey, looking into this now, do give me some time

#

What do you mean by

subscription_schedule table.
Do you mean Sigma?

left basin
lyric marlin
#

Thanks. But we used Data Pipeline

#

Is the schema for data pipeline transmission consistent with Sigma?

#

Still here?

left basin
lyric marlin
#

Thanks. But why aren't key fields, such as status, exposed? For example, subscription_schedule.status.

left basin
#

Can you tell me the use case of status so that I can pass along your feedback to the sigma team?

lyric marlin
#

I want to quickly retrieve active subscription schedules, excluding completed or canceled records.