I need to make some changes to a Bot in existing app that has been working for some time. The Bot initiates a process that runs two tasks consecutively and I need to add a third task (for testing before I delete one of the existing tasks). I have tried to do that two ways. First I tried to duplicate an existing task, modify it and then add it to the process using the Add a Step button. And the other way was to use the Add a step button and create the task afresh from scratch. Both steps are giving rise to the following oddities.
-
The newly created task has the Linking on Button greyed out

-
Both options come up with the same error message, not allowing me to save or compile the app: “error 403: something went wrong and your changes couldn’t be saved. please try reloading the page or contacting support.”
Can anyone help me identify what I may be doing wrong?
Not sure, if this is same issue or not related but I am also getting the same error (403) in automation while trying to add a template in the email attachment section of the bot. I am performing this operation as a coauthor of the app.
Typically 403 error is related to Google drive permission errors.
Issues with Google Drive - AppSheet Help
The last post in the thread below.
Please take a look a the last post in the thread below.
Please remove substantial restrictions that exist … - Google Cloud Community
The two instances of the same error 403 maybe or may not be related. However, definitely the coincidence of this same error taking place in quick succession in the automation section for both these reported incidences may be worth looking into.
1 Like
Thanks Suvrutt. The scenario you describe is exactly the one I have encountered - I was trying to add a template in the email attachment section of the bot. It appears a co-author is not truly a co-author, but merely a contributor with some privileges. I will have to log in as author to fix this.
1 Like
Thank you Rob for the update. Our scenario seems to be identical then. Let us hope the AppSheet dev team will make it a better process of coauthoring an app.
Hi Rob,
Just an addition to the post that, it will be great if you could post back , if as an author of the app, the error vanished for you. That will confirm that the issue is with “Coauthor” permissions.
Also if you also feel that coauthor permissions should be more liberal, then I would request you to like my post referred below.
Please remove substantial restrictions that exist … - Google Cloud Community