During the beta period for scheduled functions in DigitalOcean, the deployer must not throw an error just because the caller is unable to list triggers. The list triggers API call is made routinely during "wipe" operations (namespace or package) or when an action is deleted. Some users won't be enabled for the triggers API, so the list request will fail. Such users don't have any triggers anyway, so the appropriate response is to return an empty list and proceed.
During the beta period for scheduled functions in DigitalOcean, the deployer must not throw an error just because the caller is unable to list triggers. The list triggers API call is made routinely during "wipe" operations (namespace or package) or when an action is deleted. Some users won't be enabled for the triggers API, so the list request will fail. Such users don't have any triggers anyway, so the appropriate response is to return an empty list and proceed.