Thanks Gabrielle. What I found was that the program was not giving the system enough time to acknowledge the change. To explain, when the DELETE command was used to remove a subaccount, there was an immediate POST to create the new subaccount in its place, which apparently did not allow enough time for replication of the removal prior to the posting of the new subaccount.
I think our issue must be replication timing, since our process was moving very quickly to both remove and restore the same person's subaccount. This was fixed by only removing what was not going to be restored and only posting what didn't exist before per that specific user. So, in essence, we needed to tighten our data processing to be more discerning as to whether the removal / post process was redundant or was instead really needed. So far, it appears the removal process and the posting process can be completely separate processes per Canvas ID, which prevents the problem I was having.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.