-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Labels
bugSomething isn't working.Something isn't working.t-toolingIssues with this label are in the ownership of the tooling team.Issues with this label are in the ownership of the tooling team.
Milestone
Description
Description
- When running an Apify Actor twice in a row using
apify run -i 'some input', the first execution works as expected, but the second one fails to load the input - it returns None. - It appears that metadata files from the previous run remain in local storage, preventing the new input from being correctly loaded.
Reproduction
import asyncio
from apify import Actor
async def main() -> None:
async with Actor:
actor_input = await Actor.get_input()
Actor.log.info(f'Input: {actor_input}')
if __name__ == '__main__':
asyncio.run(main())uv run apify run -i '{ "days_reminder_long": 2000, "days_reminder_short": 2000, "days_urgent": 2000 }'
uv run apify run -i '{ "days_reminder_long": 2000, "days_reminder_short": 2000, "days_urgent": 2000 }'
Expected behavior
- Each run should receive the provided input, regardless of previous executions.
Actual behavior
- First run works correctly and logs the input.
- Second run logs
Input: None. - It seems that leftover metadata files from the first run are not cleared and interfere with input loading.
Metadata
Metadata
Assignees
Labels
bugSomething isn't working.Something isn't working.t-toolingIssues with this label are in the ownership of the tooling team.Issues with this label are in the ownership of the tooling team.