Timeout Error When Querying/Editing Data

Question

I constantly receive Time-out errors and sql transaction errors when performing edits/queries on feature services hosted on AGOL.

Is there any way around this OR what are the limitations to querying and editing?

Examples of SQL transaction Error (Note: I am only querying 1000 features with the script tha tis returning these errors):

* This SqlTransaction has completed; it is no longer usable.
* RuntimeError: This SqlTransaction has completed; it is no longer usable.
Unable to apply edits.

JBeasley · Answer

I am also getting this error inconsistently. Back to back runs of a process can have different results. I am working with AGOL and am performing deletes, never more than 250 features at a time. Unsure what to do to avoid this...

abrown8 · Answer

I'd also love to know if this got solved - I've also started to get this same error 'This SqlTransaction has completed; it is no longer usable.' but on large tables (> 2mil entries). Wondering if it's timing out?

matthewpgrasso · Answer

Hi @PatrickFilyer --I know you posted this a while ago, but it's still an issue today, at least for me. Did you ever find an explanation for this? I get this often as well. Seems to happen randomly. Sometimes I won't get this error for months and then it'll pop up again on the same, unaltered, code. Thank you!