Skip to content

fix: allow running Actors and tasks without input - #84

Merged
vdusek merged 3 commits into
mainfrom
fix/allow-empty-input
Oct 29, 2026
Merged

vdusek merged 3 commits into
mainfrom
fix/allow-empty-input

Conversation

@vdusek

@vdusek vdusek commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

ApifyDatasetFromActorCall and ApifyDatasetFromTaskCall raised a ValueError when neither the constructor nor run got any input, and {} counted as no input too. That blocked running a saved task with its saved input, which is the main reason to use a task, and running an Actor whose input fields all have defaults.

Both components now skip the check and start the run with no input when the merged input is empty. The task uses its saved input, and the Actor uses its defaults or fails the platform's input validation. The same applies to run_async.

Reported in the review of apify/apify-docs#3116: apify/apify-docs#3116 (comment)

✍️ Drafted by Claude Code

@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Oct 29, 2026
@vdusek vdusek self-assigned this Oct 29, 2026
@vdusek
vdusek marked this pull request as ready for review October 29, 2026 12:23
@vdusek
vdusek merged commit 3036312 into main Oct 29, 2026
26 checks passed
@vdusek
vdusek deleted the fix/allow-empty-input branch October 29, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant