I need help in identifying a root cause of an issue with a zap being flooded of execution for a single job.
the situation is that I have a servicem8 connected to a zapier that checks for job completion. on May 19, a single job was set to completed everything was good and job was detected by the connected zap via the “job completed” native action zapier.
But the issue occurred when zapier received the signal 1000 times in a span of 2 minutes, this burnt trough all our task credits in zapier as the zap fired all the task for the same job UIID in a very short period of time. what could have happened here and what can i do to trace the issue if it occurred in servicem8 or zapier itself.
To narrow down whether the repeats came from ServiceM8 or downstream in Zapier, it helps to first confirm what ServiceM8 recorded for that job’s status change.
Check the job’s Diary for “Status Changes” entries (this visibility is controlled by the Security Role setting “Show Status Changes”).
If you’re checking via API, GET /job/{uuid}.json returns the job status, plus completion_date (when the job was marked Completed) and completion_actioned_by_uuid (who marked it completed).
If your Zapier connection is using ServiceM8 webhooks, ServiceM8 sends a HTTP POST to the callback URL each time a subscribed field changes.
With ServiceM8 webhooks, the callback URL should return HTTP 200, and 4xx/5xx responses are retried, so any receiver errors/timeouts can result in repeated deliveries.
You can also review account-level events (including add-on activated/deactivated) in Settings > ServiceM8 Account > View Account Activity; the log retains 90 days and can’t be exported.
If you email support@servicem8.com with the job UUID and the approximate timestamp of the spike (rather than posting account-specific details publicly), we can advise on next steps from what’s visible on the ServiceM8 side.