Zapier not receiving response from IO, so multiple leads created
Hi IO team,
I'm using Zapier to create leads in IO via the "InflatableOffice (1.0.0)" Zapier integration. We've been seeing several instances in the past few weeks where Zapier will attempt to create a lead in IO, and then returns the error message "The app did not respond in-time. It may or may not have completed successfully", even though the IO lead was indeed created. So Zapier waits a while and tries again, returns the same error message, and the loop continues, creating a new lead with each loop until finally it registers a response from IO that a lead has been created and the loop closes. Today, a single Zap run created leads 18775093, 18767495, 18764733, and 18762927, when only one lead should have been created. This is causing problems downstream for us. Can you help?
The same question
I have out developers looking into this and advise if they are able to provide any assistance.
I have out developers looking into this and advise if they are able to provide any assistance.
Please see my video response and provide the additional requested data. Thanks.
https://www.loom.com/share/f8acdf8fa93640008f1811bc47be5949
Please see my video response and provide the additional requested data. Thanks.
https://www.loom.com/share/f8acdf8fa93640008f1811bc47be5949
Thanks very much for your response, Tim! To answer your first question, it's not always exactly four leads that are generated. Sometimes it's two, or three, or four leads. I see for failure #3 in the list below, two leads were created. I'd like to be able to point you to other examples, but we tend to delete the unnecessary leads when this happens, so I don't have much hard data at the moment.
Looking at the history for the relevant Zap, I'm seeing four recent instances of this issue (and many more instances where everything worked perfectly). In each failed instance, when I look at the step where the Zap sends the lead data to IO, I see entries under "Data In" (I've pasted the entries below), but there's no "Data Out" entry at all. Where the Data Out would be, it just says "Troubleshoot (Beta)", and above is the message "The app did not respond in-time. It may or may not have completed successfully." I've dropped a screenshot below.
I look forward to hearing your thoughts.
Best,
John
Here is the "Data In" entry for failure 1 (Zap triggered 2023-08-18 22:21:55). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18619315 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
eventstarttime_text:
Fields with no value:
organization
guests
venuename
Here is the "Data In" entry for failure 2 (Zap triggered 2023-08-18 13:57:56). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18611601 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Here is the "Data In" entry for failure 3 (Zap triggered 2023-08-23 15:29:16). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that two leads were created: 18764733 at 12:06pm, and 18786447 at 10:08 pm.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Here is the "Data In" entry for failure 4 (Zap triggered 2023-08-24 23:10:40). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18816829 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Thanks very much for your response, Tim! To answer your first question, it's not always exactly four leads that are generated. Sometimes it's two, or three, or four leads. I see for failure #3 in the list below, two leads were created. I'd like to be able to point you to other examples, but we tend to delete the unnecessary leads when this happens, so I don't have much hard data at the moment.
Looking at the history for the relevant Zap, I'm seeing four recent instances of this issue (and many more instances where everything worked perfectly). In each failed instance, when I look at the step where the Zap sends the lead data to IO, I see entries under "Data In" (I've pasted the entries below), but there's no "Data Out" entry at all. Where the Data Out would be, it just says "Troubleshoot (Beta)", and above is the message "The app did not respond in-time. It may or may not have completed successfully." I've dropped a screenshot below.
I look forward to hearing your thoughts.
Best,
John
Here is the "Data In" entry for failure 1 (Zap triggered 2023-08-18 22:21:55). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18619315 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
eventstarttime_text:
Fields with no value:
organization
guests
venuename
Here is the "Data In" entry for failure 2 (Zap triggered 2023-08-18 13:57:56). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18611601 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Here is the "Data In" entry for failure 3 (Zap triggered 2023-08-23 15:29:16). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that two leads were created: 18764733 at 12:06pm, and 18786447 at 10:08 pm.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Here is the "Data In" entry for failure 4 (Zap triggered 2023-08-24 23:10:40). Zapier has no entry for Data Out, but it must have been successful at some point, because I see that lead 18816829 was created.
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Thanks for the detailed information. Based on what you sent, I would guess these are occurring during times when our server is having issues. Please post the next one that occurs, especially the time that the attempt is made. Thanks!
Thanks for the detailed information. Based on what you sent, I would guess these are occurring during times when our server is having issues. Please post the next one that occurs, especially the time that the attempt is made. Thanks!
Hi Tim,
I've just seen an occurrence of this. From a single trigger, Zapier created four leads (details below). Like last time, I'm seeing the same error message in Zapier, except this time, the Zap is not yet done it's attempts, and the next attempt is scheduled for 2023-08-30T21:54:36.985940Z. I've pasted a Zapier screenshot, the IO lead details, and the Zapier "Data In" details below.
IO LEAD DETAILS:
19005265 (created 08/30/20231:17 pm)
19005487 (created 08/30/20231:39 pm)
19006485 (created 08/30/20231:53 pm)
19008969 (created 08/30/20232:54 pm)
ZAPIER DATA IN DETAILS:
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
Hi Tim,
I've just seen an occurrence of this. From a single trigger, Zapier created four leads (details below). Like last time, I'm seeing the same error message in Zapier, except this time, the Zap is not yet done it's attempts, and the next attempt is scheduled for 2023-08-30T21:54:36.985940Z. I've pasted a Zapier screenshot, the IO lead details, and the Zapier "Data In" details below.
IO LEAD DETAILS:
19005265 (created 08/30/20231:17 pm)
19005487 (created 08/30/20231:39 pm)
19006485 (created 08/30/20231:53 pm)
19008969 (created 08/30/20232:54 pm)
ZAPIER DATA IN DETAILS:
rental_names:
taxexempt:
eventduration:
locationid:
name:
cellphone:
email:
eventstartdate_text:
eventzip:
organization:
notes:
deliverytype:
referral:
street:
city:
state:
zip:
eventstreet:
eventcity:
eventstate:
eventcountry:
country:
salesrep:
surface:
guests:
eventstarttime_text:
venuename:
John, I noticed you are using our first Zapier app 1.0.0. I'd recommend you upgrade to using version 1.2.5 as our API and Zapier app has changed a lot since then. I'm not quite sure how you do that in Zapier, but I can assist as needed. There may be some different input requirements with the newer app. Let's start there to see if that resolves the issue.
John, I noticed you are using our first Zapier app 1.0.0. I'd recommend you upgrade to using version 1.2.5 as our API and Zapier app has changed a lot since then. I'm not quite sure how you do that in Zapier, but I can assist as needed. There may be some different input requirements with the newer app. Let's start there to see if that resolves the issue.
Replies have been locked on this page!