You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a feeling I am trying to shove too much information too quickly, or incorrectly, to my google spreadsheet. When I try to do some basic stress testing I eventually get the error.
It looks like the error is from a conflict.
I am loading an upload queue which when and object is pulled from it I get about 4 points of information from it and upload each cells updates individually. I am thinking google might prefer that I update a range of cells, which I am guessing might reduce overhead. Before I spent too much time guessing and checking I figured I might get some input on how this might be happening and how to handle it.
The text was updated successfully, but these errors were encountered:
I have been looking through my code, it looks like I might have had a call to create new row outside of my queue that could of possible caused the conflict. I have to change my program flow some and hopefully report good new later today.
I think I did pinpoint it. Have not got too much farther and restructuring my code now to better manage calls to google docs. If you have not really seen this before I am pretty sure I have resolved the issue.
I have a feeling I am trying to shove too much information too quickly, or incorrectly, to my google spreadsheet. When I try to do some basic stress testing I eventually get the error.
It looks like the error is from a conflict.
I am loading an upload queue which when and object is pulled from it I get about 4 points of information from it and upload each cells updates individually. I am thinking google might prefer that I update a range of cells, which I am guessing might reduce overhead. Before I spent too much time guessing and checking I figured I might get some input on how this might be happening and how to handle it.
The text was updated successfully, but these errors were encountered: