Select to view content in your preferred language

Send Error: Layer "_" not found in feature service

3744
13
Jump to solution
07-24-2023 10:26 AM
ClaireField
Occasional Contributor

Hello and Happy Monday. 

I have attached a screenshot to this post to highlight my error. The survey (created on connect) worked on Friday, submitted a few surveys, but no longer works today per the error in the screenshot. This has happened numerous times so far and the only fix is to delete the feature layer and republish. This isn't bad as I keep having to change variables and most of it was just trial and error. As I come to a close on this project, I would like to hear if anyone else has dealt with this problem.

I found a 2018 post : Survey123: Send Error - Layer 'XYZ' not found in the feature service which was solved by the individual stating they logged out and restarted their device to fix it. I tried it myself and it did not work.

The feature layer is active.

Thank you for any assistance.

0 Kudos
13 Replies
GISAdminTT
New Contributor

Hi, I recreated and republished my survey with a different name yesterday. Shared and tested with multiple users in my organization and it worked fine.

Just tried it again and the error has recurred.

Again, this only happens in the field app; I'm still able to submit through the web app.

Wondering if it's a problem with the latest update... Field app version 3.18.142 (tested on pc and apple device)

Please let me know if the problem recurs for you too

 

DougYurek
Occasional Contributor

We are seeing the same issue, I have a survey that works most of the time but then all of the sudden it will start displaying the Send Error - Layer 'XYZ' not found in the feature service.

Sometimes, restarting the Survey123 app fixes the issue. Other times, I have to sign-out/in, delete the survey, reinitialize the database...and then it will work, before breaking again. 

  • Connected to Wifi
  • It will work one minute, then break again.
  • Inbox fails to refresh during this time, frozen screen.
  • I know the feature service is up, as the survey-form itself makes 'pulldata' requests to the same URL. Plus, I have full admin to the back-end and have verified everything I can.

I have a ticket open with premium support and will share anything useful I find. 

 

SMH-Rio
Frequent Contributor

I had the same problem and I was only able to resolve it by publishing a new survey with a different name (apart from all the work of recovering old data, repointing webmaps, dashboards, etc.).

Below is the history of the problem and the tests I carried out:

1 - Initially, opening the field app through the URL gave an error, while opening the application directly through Windows worked. To correct the error, simply close and open the field app again and send the records from the Outbox;

2 - At a certain point, opening directly through Windows also started to give an error;

3 - I removed the submission_url from the form and, even pointing to the "original" layer, the error persisted (both opening via link and via Windows);

4 - I created a new form, with a different name, pointing to the "original" visualization layer (through submission_url) and the error persisted (both opening via link and via Windows);

5 - Finally, I decided to publish a new search and a new layer and, for now, it stopped giving errors (it works by opening the form via link and through Windows)

 

Update: after creating a view of the new layer and pointing it to the submission_url, the problem returned 🙄

0 Kudos
ScottJones1
Frequent Contributor

did you ever find a solution? I just updated my survey, for it to publish I had to change the name of my table (which for reasons I dont remember had adjusted the name). This allowed me to publish without deleting all of my data. But now I am getting the dreaded, Layer not found...

0 Kudos