Questions about team folder api

[hhting]

1. When I utilize the "/team_folder/archive/check" API to verify the status of the asynchronous archive job, I receive the following response:
the ".tag" suggests that the job is complete, but the status tag is "archive_in_progress". Which status should I trust?

{

".tag": "complete",

"team_folder_id": "2325974275",

"name": "test_archive",

"status": {

".tag": "archive_in_progress"

},

"is_team_shared_dropbox": false,

"sync_setting": {

".tag": "default"

},

"content_sync_settings": []

}

2. When will the async archive job trigger long poll api:
at completion of the async archive job or at the moment when we send the async archive api?

3. Is the team folder id identical to share_folder_id that returned in FolderSharingInfo?

[Greg-DB]

1. I'll check with the team on this to see if we can get some better clarity on this.

2. The /2/files/list_folder/longpoll functionality should trigger shortly after any changes in the relevant account's filesystem, based on the account connected to the cursor that was used. So in this case, that means that should fire shortly after the team folder is removed from the account folder structure.

3. Yes, a team folder ID is a type of shared folder ID.

[hhting]

>  that should fire shortly after the team folder is removed from the account folder structure.
This would happen whether the async archive job has completed or is still in progress?

Seems that after the async archive job API is sent, the list folder API (with include_deleted = false) will not include the team folder that is archived in progress?

[Greg-DB]

Archiving a team folder removes it from all members' folder structures, and accordingly further results from the list_folder functionality would then reflect that, but I don't have a more specific guarantee or documentation on the exact timing of when that occurs in that process.