ServiceM8 Custom Addon Stability Issue – Automatic Removal of Addon and Code

General
1

Hi,

I hope you are doing well.

I would like to report an issue we are experiencing with the custom ServiceM8 addon and request your assistance in investigating the root cause.

Issues Observed

1. Custom Addon Gets Uninstalled Automatically

  • The custom addon is successfully installed and functions as expected initially.
  • However, after a period of time, the addon appears to be automatically removed/uninstalled from the ServiceM8 account without any manual action from our side.
  • This behavior is affecting the stability and availability of the addon for end users.

2. Custom Addon Code Disappears Automatically

  • We have also noticed that the code associated with the custom addon is vanishing after some time.
  • The addon files and configurations are present and working correctly after deployment, but later become unavailable without any intentional modifications or updates.
  • This results in the addon no longer functioning as expected and requires redeployment to restore functionality.

Additional Information

  • The issue has occurred multiple times.
  • No manual uninstallations, deletions, or code removals have been performed by our team.
  • The addon works correctly immediately after installation/deployment and only disappears after some time has passed.

Could you please investigate whether there are any platform restrictions, automated cleanup processes, deployment limitations, account-level policies, or other factors that could be causing the addon installation and code to be removed automatically?

We would appreciate any logs, diagnostic information, or recommendations that can help identify and resolve this issue permanently.

Thank you for your assistance, and please let us know if any additional information is required from our side.

Kind regards,
Bruno

2

Yea i’ve got the same happening on my account and just posted about the same thing:

In my case it’s been happening for months.

3

Hi Bruno,

This is account-specific, so the best next step is to email support@servicem8.com rather than sharing deployment details publicly. For context, ServiceM8 add-ons can be Simple Function add-ons hosted on ServiceM8 infrastructure, AWS Lambda add-ons, or web-service hosted add-ons, so the checks are different depending on how yours is deployed.

For a Simple Function add-on, ServiceM8 manages the infrastructure, you supply the code, and the code is edited from the Edit Function button in the add-on settings page.

Before emailing, check Settings > ServiceM8 Account > View Account Activity and search the relevant time window for add-on activated/deactivated events: How to view your Account Activity - ServiceM8 Help Center. Account Activity includes the action, user, IP/location, and time, and add-on activated/deactivated events include third-party add-ons and API approvals.

If your add-on uses webhooks, also check the webhook status, because 4xx/5xx callback errors are retried for up to 72 hours before automatic cancellation, and inactive webhook subscriptions can be inspected with GET /webhook_subscriptions?status=inactive.

When you email Support, include the add-on name/ID, whether it’s Simple Function/AWS Lambda/web-service hosted, approximate date/time/timezone, screenshots of the custom add-on status/details, any Account Activity rows for activation/deactivation, and any webhook/callback failure details if relevant. Remove API keys, App Secrets, full JWTs, access tokens, session strings, and customer/job personal data before sending anything.

Thanks,
Cody