Keep3r Autotask errored with "INVALID_ARGUMENT","reason":"invalid ENS name"

Thanks for your reply. After reading it, I created a new autotask and put the code in again and it worked!!! Previously, I just the code from the guide into an existing autotask I created a few days ago. I’m not sure how that is any different but I’m ecstatic that it worked.

2020-11-05T03:55:27.641Z	AUTOTASK START
2020-11-05T03:55:30.742Z	INFO	========= NOTICE =========
2020-11-05T03:55:30.742Z	INFO	Request-Rate Exceeded  (this message will not be repeated)
2020-11-05T03:55:30.742Z	INFO	
2020-11-05T03:55:30.742Z	INFO	The default API keys for each service are provided as a highly-throttled,
2020-11-05T03:55:30.742Z	INFO	community resource for low-traffic projects and early prototyping.
2020-11-05T03:55:30.742Z	INFO	
2020-11-05T03:55:30.743Z	INFO	While your application will continue to function, we highly recommended
2020-11-05T03:55:30.743Z	INFO	signing up for your own API keys to improve performance, increase your
2020-11-05T03:55:30.743Z	INFO	request rate/limit and enable other perks, such as metrics and advanced APIs.
2020-11-05T03:55:30.743Z	INFO	
2020-11-05T03:55:30.743Z	INFO	For more details: https://docs.ethers.io/api-keys/
2020-11-05T03:55:30.743Z	INFO	==========================
2020-11-05T03:55:34.916Z	INFO	Bonded relayer: 0x5030072fca3208f9a8e37bf2b58a89a376ce4020ac0a23ac154e3654ec4c0150
2020-11-05T03:55:34.918Z	AUTOTASK COMPLETE

So now I get this message about throttling. I’m not sure if it means my autotask will be throttled. How can keepers we get around the throttling issue?

Also noticed the bonded relayer address in the log doesn’t correspond to the address of the relayer I created. Is this to be expected?

1 Like