#stefan-colic_docs

1 messages · Page 1 of 1 (latest)

main hatchBOT
minor iglooBOT
#

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.

main hatchBOT
#

👋 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/1270294592087916574

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

true dirge
#

👋 happy to help

#

The currently_due requirements request only the user information needed for verification at this specific point in time;
the eventually_due requirements include a more complete set of questions that we’ll eventually need to collect.

#

If the account contains any currently_due fields when the current_deadline arrives, the corresponding functionality is disabled and those fields are added to past_due

civic olive
#

I see that in all events current_deadline is null. Does that explain why currently_due, eventually_due and past_due are the same?

true dirge
#

would you mind sharing an example?

civic olive
true dirge
#

if the requirements.past_due is not empty this means you need to start with these requirements first

#

then the currently_due

#

then the eventually_due

#

also you can see that the account was disabled because the some requirements were past_due
"disabled_reason": "requirements.past_due",

civic olive
#

I guess it has to do that this is test mode. So it's not a live standard account.

#

When i filled in everything, the disabled_reason went to null

true dirge
#

yes because the account's status has changed

#

and it's no longer disabled

civic olive
#

What are the differences between requirements and future_requirements?

true dirge
#

future_requirements are upcoming new requirements that even if they don't get collected the account won't be disabled

#

it includes what information needs to be collected, and by when.