Repository navigation
fix: allow running Actors and tasks without input - #84
Merged
Merged
Conversation
vdusek
marked this pull request as ready for review
October 29, 2026 12:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ApifyDatasetFromActorCallandApifyDatasetFromTaskCallraised aValueErrorwhen neither the constructor norrungot 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