Automating report creation for survey using Make (Integromat), getting a runtime error

[AaronManuel2]

Hi all, I'm trying to create a scenario in Make (formerly Integromat), that watches a survey with a webhook. When it gets a new survey, the scenario adds a row to a google doc, makes a report, then uploads the report to a google drive and sends an email.

I have most of the pieces working but the survey123 report module itself is returning a runtime error, an empty result - "[]". The scenario itself is not that complicated and to start I followed this Esri video here - https://www.youtube.com/watch?v=a7pABoinPlM , though I realize this video is getting a bit old now.

I attached a photo with my settings for the module

I believe what I have here for feature objectid is correct. I don't think I need a where clause since I'm only trying to pull in the new survey from the webhook. 

I know this could be a make problem but I put in a ticket with them and they showed me the issue in the api response log is just 'there is no record in the query result'. So I am doing something wrong with the objectid selection but I'm not sure how.

Anyone have a scenario going with Make thats creating reports successfully? 

[TrafficOpsGIS]

Since yesterday I am unable to access to Report Link in Survey123 web. Has not been working in a report dashboard we have configured either. Think they broke something and didn't tell anyone. Best of luck. Hope they get resolved soon.

[AaronManuel2]

Hmm thanks for the info. What adds to this is that when I first built this scenario a week or so ago, it was working, then it suddenly stopped.

[AaronManuel2 · Accepted solution]

All, I did end up fixing this by rebuilding the make scenario piece by piece and it works now. The other thing I realized is that in the survey123 webhook settings, this survey had about 6 or 7 webhooks attached to it that were still active from when the survey was originally created some time ago. Maybe this was causing an issue. So I also deleted all the extra webhooks.

Doesn't make sense to me that this would fix the report creation module though since its not the piece actually reading the payload information from the webhook.