Google Ads Keywords-for-Keywords
Pricing
$0.10 / actor start
Discover related keywords for any seed keyword with Google Ads search volumes, CPC, competition, and 12-month monthly trends. 217 countries × 46 languages.
Pricing
$0.10 / actor start
Rating
0.0
(0)
Developer
wang wei
Maintained by CommunityActor stats
0
Bookmarked
9
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
LIMITED_PERMISSIONS — how Apify's automated QA and every API-triggered run
starts an Actor — opening the store is refused with HTTP 403
(KeyValueStoreCollectionClient.getOrCreate, path /v2/key-value-stores).
That call sat in a || fallback chain and was never inside a try/catch of
ours, so the throw ended the run with exit code 91 and a reported FAILED run
with zero items. Every store open now goes through a wrapper that returns a
no-op store instead of throwing, so the free-run counter and the run SUMMARY
degrade and the actual work proceeds./v2/key-value-stores; it used a fixed limit=50, which silently
stopped containing gate stores once the account passed 50 of them — and the
account creates a new default store on every run, so that list grows on its
own. The lookup now pages (100 per page, up to 20 pages).Actor.setValue does not just fail
under LIMITED_PERMISSIONS — it can simply never resolve. Measured on a live
run of a sibling Actor: results were fetched successfully, then the following
setValue never returned and the run sat for 49 minutes before being aborted
with an empty dataset and a $0.08 bill, and not one error in the log.
try/catch cannot help with that — it catches a rejection, not a promise that
never settles, so the previous try { await Actor.setValue(...) } catch {...}
guard was not sufficient. SUMMARY now races a 15s timeout and reports the
failure, so a stuck store costs one summary field instead of the whole run.makeLogger gained the missing warning level. @apify/log exposes
warning and leaves warn undefined, so every logger.warning(...) call
threw a TypeError — including inside the free-tier gate's own "I am degrading"
branch, which meant the run died while reporting that it was degraded.validateInput is now exported, so test/expand-tasks.js can assert on it.free_tier_cap with enforced / degraded /
degraded_reason, so a cap that stopped being enforced is visible outside
the log.Date From and Date To input fields for monthly search-history selection.Target Language dropdown covering 20 major languages.monthly_searches and concepts arrays remain queryable.