feat(actors): enables standby mode via actor.json #991

l2ysho · 2026-01-13T20:30:03Z

Fix usesStandbyMode not being applied when pushing Actor via CLI

Problem

When creating an Actor locally using apify create my-actor -t ts-mcp-server and then pushing it with apify push, the usesStandbyMode: true setting from actor.json was being ignored. The Actor would be created on the platform without standby mode enabled, even though the template explicitly sets this option.

In contrast, cloning the same template directly from the Apify Console UI correctly enabled standby mode.

Root Cause

The push command was not reading the usesStandbyMode property from actor.json and was not passing it to the Apify API when creating or updating Actors.

Solution

Added DEFAULT_STANDBY_OPTIONS constant with all required API fields for standby mode configuration
When creating a new Actor, if usesStandbyMode: true is set in actor.json, the standby options are passed to the API
When pushing to an existing Actor that doesn't have standby enabled but usesStandbyMode: true is in actor.json, the Actor is updated to enable standby mode

Changes

src/commands/actors/push.ts: Added standby mode support for both new and existing Actors
test/api/commands/push.test.ts: Added two API tests to verify standby mode is correctly enabled

Testing

apify create my-actor -t ts-mcp-server
cd my-actor
apify push

The Actor should now have standby mode enabled with the default configuration.

closes #913

l2ysho · 2026-01-13T20:32:26Z

Keeping this as draft, it is working but it seems we missing some types in apify-client, lets discuss.

src/commands/actors/push.ts

l2ysho · 2026-01-15T11:16:24Z

lest's wait for #992 merged and then rebase

Enables standby mode for Actors based on the 'usesStandbyMode' property in actor.json. If the property is set to true during Actor creation or update, standby mode is enabled with default configuration. Fixes #913

janbuchar

It's great that you are fixing this! Consider this approved by me once @vladfrangu approves it, I don't have anything to add beside that one comment.

src/commands/actors/push.ts

…not-work

B4nan · 2026-01-27T15:12:30Z

package.json

        "adm-zip": "~0.5.15",
        "ajv": "~8.17.1",
-        "apify-client": "^2.14.0",
+        "apify-client": "2.22.0",


same as with the other PR

Suggested change

"apify-client": "2.22.0",

"apify-client": "^2.22.0",

(you will need to regenerate the lockfile after this iirc)

I did a similar change in #1004 with ~ 😄

yop, my bad, I used ni apify-client@2.22.0. #1004 is merged so i will sync this. Before that there was ^ so stick to that?

I'd go with ^ personally, but no strong opinions about it.

ok lets go Vlads way then, as it is already in master

Just keep in mind that it means we'll need to adjust the conditions again on next feature release. And as you can see, we often ship feature bumps in the client.

hm, ok so ^ seems better option

Yes, I'd say so. For the CLI it's not that important, since the bundled versions will always use what is bundled anyway, but for those installing via NPM it can help.

vladfrangu · 2026-01-27T15:13:13Z

src/commands/actors/push.ts

+				// Enable standby mode if configured in actor.json
+				if (actorConfig!.usesStandbyMode) {
+					newActor.actorStandby = { isEnabled: true };
+				}


Just calling out, not blocking: This will only enable standby on new actors, and it will NOT propagate to existing ones (say if you migrate from ??? -> standby, or vice versa)

Maybe this is something we want to do? @B4nan Or should it be a different command, like actors edit?

Hmm, good point, no strong opinions, I wouldn't add a new command for that (we don't have actors edit, or do we?)

(I wouldn't block the PR on that, it can happen in a future one, or even never if nobody really asks for it)

I mean, there are other cases already where changing something in the actor.json file for an existing Actor doesn't change the "platform-side version" of the Actor, so... Ostrich algorithm?

Yeah agreed, lets leave that for ~~later~~ never.

…not-work

vladfrangu · 2026-01-27T15:55:27Z

Cases which have an issue actually to deal with and implement... 🫠 We can deal with that theb

…

On Tue, Jan 27, 2026 at 17:53 Jan Buchar ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/commands/actors/push.ts <#991 (comment)>: > + // Enable standby mode if configured in actor.json + if (actorConfig!.usesStandbyMode) { + newActor.actorStandby = { isEnabled: true }; + } I mean, there are other cases already where changing something in the actor.json file for an existing Actor doesn't change the "platform-side version" of the Actor, so... Ostrich algorithm? — Reply to this email directly, view it on GitHub <#991 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEJA4MFDELNE5YAYGWY4M2T4I6CXHAVCNFSM6AAAAACRSZV6P6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTOMJSGAYTKMZVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

…not-work

l2ysho linked an issue Jan 13, 2026 that may be closed by this pull request

actor.json option usesStandbyMode does not work #913

Closed

l2ysho requested a review from B4nan January 13, 2026 20:30

github-actions bot assigned l2ysho Jan 13, 2026

github-actions bot added this to the 132nd sprint - Tooling team milestone Jan 13, 2026

github-actions bot added t-tooling Issues with this label are in the ownership of the tooling team. tested Temporary label used only programatically for some analytics. labels Jan 13, 2026

l2ysho commented Jan 13, 2026

View reviewed changes

src/commands/actors/push.ts Outdated Show resolved Hide resolved

l2ysho commented Jan 13, 2026

View reviewed changes

src/commands/actors/push.ts Outdated Show resolved Hide resolved

l2ysho added 4 commits January 15, 2026 12:48

feat(actors): enables standby mode via actor.json

bcb8702

Enables standby mode for Actors based on the 'usesStandbyMode' property in actor.json. If the property is set to true during Actor creation or update, standby mode is enabled with default configuration. Fixes #913

chore(actors): fix tests and remove unused type

98e9f79

chore(tests): fix path in tests

ffbf2f9

Ffx(actors): corrects standby mode behavior

dd47acb

l2ysho force-pushed the 913-actorjson-option-usesstandbymode-does-not-work branch from 1413949 to dd47acb Compare January 15, 2026 13:06

l2ysho marked this pull request as ready for review January 15, 2026 14:25

l2ysho requested a review from janbuchar January 15, 2026 14:25

l2ysho removed a link to an issue Jan 15, 2026

actor.json option usesStandbyMode does not work #913

Closed

l2ysho linked an issue Jan 15, 2026 that may be closed by this pull request

actor.json option usesStandbyMode does not work #913

Closed

janbuchar reviewed Jan 15, 2026

View reviewed changes

src/commands/actors/push.ts Outdated Show resolved Hide resolved

l2ysho added 3 commits January 27, 2026 13:29

refactor: remove defaults for standBy

3b686b1

Merge branch 'master' into 913-actorjson-option-usesstandbymode-does-…

b1ac83e

…not-work

chore: updates apify-client to v2.22.0

f97a2e4

B4nan reviewed Jan 27, 2026

View reviewed changes

vladfrangu reviewed Jan 27, 2026

View reviewed changes

Merge branch 'master' into 913-actorjson-option-usesstandbymode-does-…

62da62e

…not-work

l2ysho requested a review from vladfrangu January 27, 2026 16:02

vladfrangu approved these changes Jan 27, 2026

View reviewed changes

B4nan approved these changes Jan 28, 2026

View reviewed changes

l2ysho added 2 commits January 28, 2026 09:03

Merge branch 'master' into 913-actorjson-option-usesstandbymode-does-…

46c4310

…not-work

Chore: updates apify-client dependency

dcc824d

l2ysho merged commit 519aa43 into master Jan 28, 2026
22 checks passed

l2ysho deleted the 913-actorjson-option-usesstandbymode-does-not-work branch January 28, 2026 09:43

feat(actors): enables standby mode via actor.json #991

feat(actors): enables standby mode via actor.json #991

Uh oh!

Conversation

l2ysho commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Root Cause

Solution

Changes

Testing

Uh oh!

l2ysho commented Jan 13, 2026

Uh oh!

Uh oh!

Uh oh!

l2ysho commented Jan 15, 2026

Uh oh!

janbuchar left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

B4nan Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

B4nan Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vladfrangu commented Jan 27, 2026 via email

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

l2ysho commented Jan 13, 2026 •

edited

Loading

B4nan Jan 27, 2026 •

edited

Loading

B4nan Jan 27, 2026 •

edited

Loading