Invalid Async Job Id fails if Access Token is Refresshed

Without more information, I can't say exactly why your folders may not have been created. There are a number of ways for a create_folder_batch job to fail, resulting in the folders not being created. Please refer to the error documentation for the /2/files/create_folder_batch and /2/files/create_folder_batch/check endpoints for information on what errors can occur

Please do try starting the job again with a new access token and check the result within the four hours that the access token is valid. (Or, use a long-lived access token instead.) If API isn't behaving as expected, e.g., if the job fails when it appears it shouldn't have, please let us know and share the output so we can check on it.

And yes, right now, the ability to check the status of an async job depends on the validity of the original access token used to start that job. If that access token is no longer valid, you won't be able to check the status of an async job, even with another valid access token for that app/user. You'd need to check the result of the job while the original access token is still valid.