You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The addon stores its settings on the form itself, not on your account. A copy of a form starts empty, so nothing you configured on the original is carried over — set the addon up again on the new form.

The addon still opens and your settings can still be saved, but nothing the addon should do after a submission happens anymore on that form. This is a known issue.

Why? A form's connection to the addon belongs to the Google account that first opened the addon on that form. That can be you or another editor of the form. Once this account uninstalls the addon, the connection is gone for good: reinstalling does not restore it, and no other editor can take it over.

What fixes it is a copy of the form:

1) Make a copy of the form

In Google Forms, click the "three dots icon" at the top right and then "Make a copy".

2) Set up the addon again on the copy

Open the addon in the copy and configure it again. A copy starts without any addon settings, so nothing from the original is carried over. Do this with the Google account that will keep the addon installed, because the first account to open the addon on the copy becomes its connection.

3) Share the new link

The copy has its own link. Share that one and stop sharing the old one.

Please be aware: the responses collected so far stay in the original form and do not move to the copy. The original form and its responses are not deleted, you can still open and export them there.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

To avoid excessive scraping requests and getting blocked, all values are cached for 24 hours.

There are three possible reasons for this error:

1) The "selector" parameter was wrong. MOST FREQUENT

Solution: An existing and valid CSS selector needs to be used.
We know it might be difficult to create working CSS selectors at the beginning.
Therefore we have created a free CSS Selector Generator tool: YouTube video.

2) The selector resp. the element does not exist anymore.

Solution: Some websites are constantly changing their CSS classes to prevent scraping.
Find a selector which stays the same.

3) The website could not be fully scraped.

Solution: Try to use the "options" parameter to set a higher level, e.g.:
=SCRAPE("https://wikipedia.org/", "h1", "level_1").
Currently the following levels are supported: level_1, level_2 and level_3

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

Credits are based on the used level within the options parameter. When no level is specified within the options parameter, then 1 credit is calculated. For level_1, 2 credits, for level_2, 2 credits, and for level_3, 10 credits are calculated.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

The most frequent cause for this behaviour is the use of not supported actions. The easiest way is to delete the Gantt sheet and create a new one via: Add-ons > Gantt Chart & Project Management by GANTTophant > Create Gantt Chart. If the Gantt sheet does already contain a lot of tasks and you do not want to start from scratch, please watch the following YouTube video to get instructions on how to repair a broken sheet.

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

• Editing within the "Editable User Area" (dark-grey border)
• Button functionalities within the sidebar

• Edit outside the "Editable User Area" (dark-grey border)
• Manually copy / paste / delete / insert entire rows
• Manually copy / paste / delete / insert entire columns

Please watch the following YouTube video to get an introduction to the addon.

The progress bar uses a "conditional format rule", which displays the progress from "0% / dark red" up to "100% / dark green".

Other collaborators also need to have the PRO license to be able to edit the Gantt sheet.

The start date can not be changed after creation, only the view start can be changed within the addon's sidebar. You have two options: 1) delete your current sheet, create a new one and choose the correct start date 2) create a new spreadsheet and create a new gantt sheet within it.

The numbers are week numbers, the letter "S" or "M" stands for "Sunday" or "Monday" which indicates the first day of the week depending on your country seetings.

For performance reasons, the project duration is limited to 15 months for free users and 27 months for PRO users.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

Google has implemented a daily quota for sending emails via addons. These quotas depend on the type of Google account used. More information can be found within the "Email recipients per day" section under the following link.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The first version of the addon applied the negative marking immediatelly after form submissen. Unfortunately this approach was not stable and therefore the manual approach was chosen.

Google has implemented a daily quota for sending emails via addons. These quotas depend on the type of Google account used: gmail.com users: 100 mails/day, Google Workspace users: 1,500 mails / day. More information can be found within the "Email recipients per day" section under the following link. If you want to increase the daily mail quota, you need to upgrade to a Google Workspace account.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

Currently there is no Google Calendar sync available. The Google Calendar icon displayed within the Google Workspace Marketplace listing reveals that the addon can be opened next to the Google Calendar.

Due to technical limitations the addon does not offer sharing the gantt chart.

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

When the addon is started the first time, a spreadsheet called "GANTTophant Reloaded - do not modify" is created and stored within your Google Drive > My Drive folder. This spreadsheet holds all your data. As mentioned within the file name, please do not modify the content of this spreadsheet or delete it. You can change the name of the spreadsheet and move it to another Google Drive folder, this will not affect the addon functionality.

This happens if you have deleted the spreadsheet "GANTTophant Reloaded - do not modify" which was created by the addon to store the gantt chart data. Open the addon again and it will create a new spreadsheet for you. Unfortunately there is no way to restore the initial spreadsheet and it's data.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

There are two options: 1) Insert the value e.g. 10,000.50 into the corresponding cell; mark the cell and choose e.g. Format > Number > US Dollar; then choose Format > Number > Plain Text 2) Write the following value into the cell (do not forget the apostrophe at the beginning) e.g. '$ 10,000.50 3) The easist approach would be to use e.g.: $ {{Total}} in your Google Docs invoice template.

Please do not insert images via: Insert > Drawing > New, instead use any other approach to insert images: a) Use Insert > Image > ... b) Insert > Drawing > From Drive. When choosing the latter option you need to first open Google Drive, click: New > More > Google Drawings and finally draw your image. Apart from images another frequent cause are missing permissions. Please make sure to open the sidebar and click the "Select" button within the "Choose invoice template" section and finaly select the currently opened Google Docs as your template. If the error "PDF Fail" still shows up, please try out the methods explained under "General Adive" on this FAQ page.

Google has limitations on the script execution: currently 6 mins. Thus the addon can only work for 6 mins which equals 20-100 invoices (depending on different factors). Then the addon needs to make a break of 1 hour until it can start again for 6 mins. And so on.

There are some edge cases where time zone compatibility issues arise and thus the date printed on the PDF invoice is one day too short / much. You can easily solve this e.g. via a formula: =TODAY()+1

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

Google has implemented a daily quota for sending emails via addons. These quotas depend on the type of Google account used: gmail.com users: 100 mails/day, Google Workspace users: 1,500 mails / day. More information can be found within the "Email recipients per day" section under the following link. If you want to increase the daily mail quota, you need to upgrade to a Google Workspace account.

The following rule is used to generate the PDF names: "Invoice " + {{Invoice Number}} If no "Invoice Number" column exists, then a timestamp will be used instead. There is currently no way to change the naming rule.

Using the ".0" and ".00" buttons in Google Sheets will only change the displayed number, not the underlying value. To change the underlying number to a specific number of decimal places, the following functions can be used. Especially ROUND() and FIXED() are useful. Please be informed that FIXED() will also round, thus it is most likely the best choice for most situations.

If one of the values within the Data Sheet is a date, the addon will format it in the following way: YYYY-MM-DD.

If you would like to use a different format, there are two possibilities:

1) Write the value as string and not as date.

2) Reformat the date value via a small formula.

No leading zeros: D - M - YYYY:

=DAY(I2) & " - " & MONTH(I2) & " - " & YEAR(I2)

With leading zeros: DD - MM - YYYY:

In both examples the cell "I2" contains the date value.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".

You can find all relevant information here.

The steps below apply to you as the document owner, not to the people using your document. Work through them in order — the first two solve most cases.

One rule holds for all of them: wherever a step asks you to test, do it on a newly created Google Forms, Sheets, Docs or Slides document, never on a copy of an existing one. Why? Many users install several addons to try them out, and each of them changes settings or the document itself. Those changes can interfere with ours, and on a fresh document they are not there.

1) Only log in with one Google Account at the same time within your browser, see example

Log out with all users except the one you work with, then test again on a new document.

Why could this solve the problem? Multi-login is not supported by Google addons, you can read more about it here and here.

2) Try another Google account, ideally a private Gmail address ([email protected]) instead of your work address ([email protected])

Create a new document under that account and test the addon there.

Why could this solve the problem? Your Google Workspace admin might have restricted specific features for your company's users. Beyond that we do not know more, but switching account has worked for a number of our users.

If this solves your issue, but your PRO licence is attached to your work email address, you can transfer your licence here.

If the addon works under the private address but not under the work address, you have hit a rare Google bug that is out of our control. We have opened two Google Issue Tracker tickets, ticket #1 and ticket #2. On ticket #1 the developer could not reproduce the issue, and neither can we; on ticket #2 Google has not started working on it yet. If you are facing this and are willing to collaborate, we are happy to open a new ticket and try to fix it together.

3) Use Chrome as your browser

Why could this solve the problem? Google products and services (and therefore also Google addons) work best within the Google Chrome browser.

4) Try the incognito mode

Open an incognito window and test on a new document.

Why could this solve the problem? Many users have installed browser plugins (e.g. ad blocker). These plugins are usually not active within incognito mode. If your plugins are also active within incognito mode, please deactivate them. If the addon works within incognito mode, it means that one of the browser plugins is causing the issue.

5) Update Chrome to the latest version

Why could this solve the problem? Usually Chrome should update itself automatically, nevertheless there are situations in which this process is disturbed. In these cases Chrome shows a red "Update" message in the right top corner. Using the latest version of Chrome guarantees having the latest features and bug fixes.

6) Remove and grant permissions again

a) Remove addon permissions at: Manage your Google Account

b) Open the addon and you will be asked again for permissions.

c) Grant permissions and make a trial run on a new document.

Why could this solve the problem? We do not know more details, but it seemed to have worked for some of our users.

7) Clear browser cache and cookies

When using Chrome the following support article describes the needed steps: Clear cache & cookies

Why could this solve the problem? This will force the browser to use the latest addon code.

8) Uninstall and reinstall the addon

Afterwards test on a new document.

Why could this solve the problem? This will force a new and clean addon setup.

9) Uninstall all other addons

Then test once more on a new document.

Why could this solve the problem? Other addons might use the same triggers / methods which might lead to interferences.

10) Move your working document to My Drive

This is the one step that is about your real document, not about a test: move it, along with all connected and required documents, to the "My Drive" location in Google Drive.

Why could this solve the problem? The folder containing your working document may have experienced permission changes. Shared Drives, in particular, use different permission structures, which could also lead to access issues.

The fix of this bug is out of our control. Just reload the page and wait 30 - 60 sec, then all menu items will show up.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

The fix of this bug is out of our control. The cause for this error message is that multiple users are logged in within the browser. You can read more about it here and here. Just log out with all users, except the one which will be used to work with the addon. Alternatively you can use a different browser or the incognito mode.

Visit My Apps, click the "three dots icon" and then "uninstall".