Hello,
I have a Make scenario that skipped to run twice. No trigger started, the Survey triggers the scenario, the Survey was submitted though.
The scenario ran one hour before and after that particular time, no events or edits were performed when the scenario was not triggered.
I have the data in the feature service that confirm that the survey was submitted and when, but that is not a log.
I need to confirm that survey was submitted. (a ticket open with Make)
Is there any way I can check?
Thanks!
Yes, but you need to enable it to start logging.
I don't use Make any more, but I assume it works the same as Power Automate's webhooks. If you made a flow, the user needs to download an update on their device to actually trigger that flow. Does the user have any pending updates to that survey?
To look at this another way, why don't you check the Portal? That will tell you when a survey was submitted.
Hi @abureaux thanks for your reply.
The scenario in Make missed two runs. It ran one hour before and after without any issue.
The survey wasn't updated, not even the scenario. Nothing happened, I was sleeping at that time.
It happened on the 8th of January, and is still running since that day. It only missed two runs.
I'd try this:
This should help narrow down the issue to the user/device, Make, or AGO/Portal.
There is a chance that Make was offline for a while. But I thought that Make had logs somewhere for that (I may be mistaken... again, it's been a while since I've done anything in Make).
@abureaux Thanks for your input,
probably two devices are using the survey and one of the two was not up-to-date.
This is the only explanation I can give to my self as the scenario triggered correctly all the times except for 2 runs only.
I'd say that in the absence of anything else, the missing update is the most likely cause. I've seen it happen with Power Automate flows before.