Apparently, Issue 1 still persists after adding privacy rule where creator of Thing can access all Thing’s field.
I got a reply from Bubble support giving feedback on the issue as follows:
TL;DR: When multiple workflows write data to the same thing (&field), sometimes you have to anticipate that data isn’t written properly.
“workflow-name” API workflow is scheduled and can see that this behavior is related to the improvements on the speed and power of scheduling an API workflow on a list. If you have an action that makes changes to the same exact thing in each instance of the workflow, then it can cause complications trying to add different things to the same field at roughly the same time (This race condition only occurs when a ‘Schedule API Workflow on a list’ action schedules an API workflow that contain an action to make changes the same thing).
So in terms of your app, since multiple instances of the “a-r-privacy-folder-files-gather-shared” API workflow is being scheduled to run at the same exact time, it is also causing actions like “add-number-scheduled” and “add-number-completed” to schedule API workflows for the same exact time as well.
A way to avoid this would be to add an interval to when you schedule the API workflow on the list to give more breathing room between each run of the workflow:
In my opinion, this is a MAJOR FLAW of the system as the program doesn’t do what it’s supposed to on a non logical basis. i.E. We cannot trust the workflow actions to execute as intended. Wdyt?