Custom AWS middleware unable to communicate with referenced REST services consistently

[CathyAlmberg]

We are using Salesforce to create a work order. Then

• AWS middleware is used to take that Salesforce data and,
• using a feature service that references a SQL SDE feature class,
• create a geometric feature populated with Salesforce data.
• Either a line or point is created.
• The geometric feature in SQL SDE is being used on a version.

Here's where we have a problem. We automate reconcile/post/compress daily at 2am. We have found that if we do not restart the REST services being written to by Salesforce/Middleware, that the Middleware request to create a feature in SDE via API, is failing.

Once the REST services are restarted, feature creation by the Middleware works again.

We are running

• ArcGIS Enterprise 11.5,
• SQL Server 2019.
• Our SDE databases are traditional versioning (not branch versioning).
• No Geometric network is involved.

[VenkataKondepati · Accepted solution]

Hi @CathyAlmberg,

I think the geodatabase nightly compression operation might be altering the state lineage which can cause persistence connection might be becoming stale or live with invalid state ids.

You can recycle the REST services after your 2AM updates so your middleware can have fresh connection to the updated database state.

Please refer the documentation below.
Administer a traditional version—ArcGIS Pro | Documentation

Reconcile and post edits to a traditional version—ArcGIS Pro | Documentation

[CathyAlmberg]

Thank you for your feedback Venkat. We have adjusted the REST service restarts to occur after the rec/post/compress, and this seems to do the trick.

Question, would branch versioning remedy this issue?

[VenkataKondepati]

I don't think so. If we have posted the edits, the problem will start.