Google Sheets Marketplace Connector Issues
I am consistently running into issues with the Google Sheets Marketplace Connector not working (i.e. hanging on import) and wondering if others have seen this or I need to change something?
In short, I am only using the "import" piece of the connector, and I can post a single record to a google sheet without any issue, however, when I run an integration and try to import it just hangs and never writes any records to the sheet. I have tried rebuilding my connection and redownloading the template, but it still just hangs when the integration is run. I do have my concurrency set at 1 based on a previous thread where Scott suggested changing this since I was getting blank rows occasionally on the sheet, so that may be one potential change I could make that I haven't tried yet.
Any suggestions on what I should try next?
Comments
Just an FYI that I asked our QA team to investigate this. There must be something specific in your flow causing the issue (that we have not tested before), and once we narrow down what it is, we will get a fix published asap.
Hey Dave Guderian, I just took a quick look at your account, and I can see 2 imports with the same name, and one of the imports is not using the latest version, and this is also the import that has been modified most recently, and so I wonder if you are accidentally using the wrong one.
Can you delete all the google sheets exports and imports in the account that originated from the marketplace, and I also highly recommend deleting all the 'script' resources as well (see pic below for the specific script to delete), and then after you have cleansed your account of all these older versions, then try downloading the marketplace integration again, and let us know if the issue is still happening.
Thanks Scott. I am going to try this and see how it goes.
Since I use the import function pretty much exclusively, I think I have got myself into this issue perhaps because of the aliasing.
Once I download the new template again, what is the appropriate way to use the import portion of the Google Sheets Integration? Should I be cloning the import step (and renaming it) for use in other flows when I need it, or do I need to go back to the marketplace each time and re-download the integration again just to get a "fresh" Google Sheet import? Again, I "think" one of the reasons why I have had so much difficulty here just has to do with the aliasing (I could be wrong), and I want to make sure I am cloning or redownloading (if needed) to avoid this issue in the future.
As always, I really appreciate the support!
Here is what I would do.
I personally hate that you need to do all this install and clone stuff, and please see the screenshot below for a feature we are planning to release this month (ETA is end of month), or worst case we will release this next month. This new feature will allow you to pick individual flow steps from the marketplace, or from your account on the fly while you are building a flow, and it will automatically do the clone as the default behavior, and it will also reuse script resources when you clone flow steps that are already in your account (vs creating copies of scripts like we do now). This feature should be a huge improvement to the UX.
If for some reason you find a bug in the import, and you need a fix for the import from the marketplace, then you will of course need to get a fresh copy from the marketplace, but this new feature we are planning will make that much much easier too.
One more helpful update. :) I uploaded a new version of the marketplace connector (just now) that does not need aliases at all, so that whole headache is gone. Hopefully you didn't see the update above and install the new version already before seeing this latest change!
Scott - No worries as I had not downloaded the marketplace template again until today.
So far, so good on this! I really appreciate the time you put into making this template so easy to work with. I have to imagine others are benefitting from it as well. Additionally, thanks for taking the time to lay out the step-by-step approach you would take. I followed each step and like I said it seems to be working as you would expect. Also, not needing to worry about the aliasing is a HUGE improvement! :)
Thanks again for your work on this!
Please sign in to leave a comment.