CertSafari
    Snowflake SnowPro Specialty: Native Apps· Lessons

    Domain 4 · Lesson 10/12

    Release channels, release directives and version management for deployed Native Apps

    Manage deployed applications.

    23 min read
    9.67% of exam
    11 sources
    Published 21 Oct 2026
    Docs as of 18 Oct 2026

    What you will be able to do

    • Choose the QA, ALPHA or DEFAULT release channel for a given audience and target accounts to it
    • Tell which channel types bill consumers and pick the channel a paying customer must install from
    • Grant the privileges that release management requires without handing over ownership
    • Tell a version from a patch and keep the version inventory within its limits
    • Set default and custom release directives, including scheduled and maintenance-window upgrades
    • Predict the pricing and trial behaviour of an app based on the channel it was installed from
    • Configure how directive changes reach consumers in remote regions through Cross-Cloud Auto-Fulfillment
    • Find release metadata and per-consumer usage metrics for installed apps

    Key concept

    Release directive (per release channel) — A release directive is the pointer that decides which version and patch a consumer installs or is upgraded to. Once release channels are enabled, each channel has its own default directive and can also have custom ones, so the version a consumer gets depends on both the channel they are in and the directive that applies to their account.

    1.Three release channels for three audiences

    Once an app is installed in consumer accounts, the provider still controls what code those accounts run. Release channels are how that control is divided by audience. A single application package can serve an internal test build, a preview build for a few customers and a production build all at the same time, each from its own channel. Release channels are on by default for new application packages. They can also be switched on later with ENABLE_RELEASE_CHANNELS=TRUE, and that choice is permanent: once enabled, they cannot be disabled.

    The channels differ in who can reach them and in what Snowflake checks first. QA is for testing inside your own organization, and even there it is opt-in: you target specific accounts in that organization, not all of them. ALPHA can go to consumers outside your organization, which makes it the channel for working with customers while the app is still in development. DEFAULT is the production channel. It is the only channel open to every consumer who has access to the listing, and everything in it has to pass the automated security scan.

    The scan also behaves differently in ALPHA and in DEFAULT. In ALPHA it runs in the background: while it is still running you can already set a release directive for the version and consumers can install it. If the version then fails, it can no longer be used. DEFAULT gives you no such window, because a version has to pass the scan before it is served there.

    How the three release channels differ
    ChannelWho can receive itAutomated security scanIntended useBilling
    QAAccounts you target explicitly, inside the provider's organization onlyNot triggeredTestingFree; does not use the listing's pricing plan
    ALPHATargeted accounts, including consumers outside the provider's organizationTriggered; consumers can install while it runs, but a failed version becomes unusableCollaboration with consumers during developmentFree; does not use the listing's pricing plan
    DEFAULTAll consumers with access to the listingMust passProductionUses the pricing plan configured for the listing

    Channel type is also a monetization decision, because it decides whether an install is ever billed. QA and ALPHA are test channels, and their installs are free: they never touch the pricing plan on the listing, whether that plan is paid or not. DEFAULT is the only channel meant for production, and every instance installed from it uses the listing's pricing plan. The failure this produces is quiet. A design partner who signs a contract but is left on ALPHA keeps running the app and is never charged, so revenue starts only once their account installs from DEFAULT.

    Every consumer can install from DEFAULT without any targeting. QA and ALPHA each keep their own list of accounts, written as organization.account. ADD ACCOUNTS adds accounts to that list and REMOVE ACCOUNTS takes them off. SET ACCOUNTS replaces the entire list, so any account you leave out of the new list is removed. Treat it as an overwrite, not an append.

    Adding a consumer account to the ALPHA channel's target listsql
    ALTER APPLICATION PACKAGE my_app_package MODIFY RELEASE CHANNEL ALPHA ADD ACCOUNTS=(ORG1.ACCOUNT1);

    Checkpoint 1 of 11· Fill the gap

    Three consumer accounts are already on the ALPHA channel's target list. The provider wants to give ORG1.ACCOUNT1 access to ALPHA as well, and the existing accounts must keep their access. Which keyword completes the command?

    ALTER APPLICATION PACKAGE my_app_package MODIFY RELEASE CHANNEL ALPHA  ?  ACCOUNTS=(ORG1.ACCOUNT1);

    Sources123

    2.Privileges for release management

    Release work does not require ownership of the package. The package-level privilege is MANAGE RELEASES. A role that holds it can enable release channels on the package and enable the QA and ALPHA channels for it. It can also register, deregister and add versions and patches, and set release directives. That makes it the natural grant for a release-manager role that should not be able to drop or reshape the package itself.

    Granting release management on one package to a dedicated rolesql
    GRANT MANAGE RELEASES ON APPLICATION PACKAGE hello_snowflake_package
      TO ROLE release_mgr;

    Two broader privileges also allow these commands. OWNERSHIP of the application package covers everything on that package. MANAGE VERSIONS is a global, account-level privilege that lets a role change release channels and release directives on *any* application package in the account. Pick by scope. MANAGE RELEASES suits one team working on one package. MANAGE VERSIONS suits a central platform role that ships every app in the account, and it should be granted rarely for exactly that reason.

    Checkpoint 2 of 11· Check yourself

    A central platform role ships every Native App in the provider account. It must be able to change release channels and release directives on all application packages in the account through one account-level grant, without owning any of the packages. What should be granted?

    Sources234

    3.Versions, patches and the stage path behind them

    Directives point at two kinds of release. A version carries major change: new features and changed functionality. A patch is a smaller update inside an existing version, such as a security fix. Patches should not change app state. Each version and each patch has its own manifest file and setup script, and one version can carry many patches, up to 130. A version identifier can be at most 30 characters long.

    The files come from a stage. In the USING clause, you give the stage path where the version's manifest, setup script and other app files are stored. It does not name accounts, a channel or a warehouse. On a package without release channels, the legacy form ADD VERSION ... USING both creates the version and points to its files. On a package with release channels, that clause is not supported. You run REGISTER VERSION ... USING instead, and the new version starts at patch 0 without belonging to any channel. When you add a patch without giving a number, Snowflake uses the previous patch number plus one.

    Legacy (no release channels): USING points at the stage holding the version's filessql
    ALTER APPLICATION PACKAGE hello_snowflake_package
      ADD VERSION v1_1
      USING '@hello_snowflake_code.core.hello_snowflake_stage';

    The full registration workflow, including labels and patch creation, is covered in Registering versions and adding patches. For a deployed app, the ongoing task is keeping the inventory small. Patches cannot be dropped, so the version is the only unit you can retire. DEREGISTER VERSION removes a version together with all its patches. It only succeeds once the version is in no release channel and no installed app instance is running on it. Make deregistering old versions a routine step so a version slot is free before the next release has to be registered.

    Checkpoint 3 of 11· Check yourself

    Version v1 of an app has no installed instances running on it, but it is still assigned to the ALPHA release channel. The provider runs DEREGISTER VERSION v1 to free a version slot. What is the result?

    Checkpoint 4 of 11· Exam question

    Which statement correctly distinguishes a version from a patch when managing an application package's release lifecycle?

    Checkpoint 5 of 11· Exam question

    A provider runs ALTER APPLICATION PACKAGE my_pkg ADD VERSION v2 USING '@my_pkg.stage.files/v2/'. What is the purpose of the USING clause in this statement?

    Checkpoint 6 of 11· Exam question

    What is the maximum length allowed for a version_identifier when registering a new version on an application package?

    Sources1532

    4.The two-version limits on assignment

    Three separate limits apply, and each one blocks a different step.

    Version limits and what each one blocks
    LimitWhat it blocksHow to free it
    At most two versions per release channelADD VERSION to a channel that already has twoDROP VERSION from that channel once consumers are off it
    At most two unassigned versions in the packageREGISTER VERSION when two registered versions are not yet in any channelDEREGISTER VERSION an unneeded one
    Only the previous version may be live when upgradingUpgrading consumers to v3 while some still run v1Migrate everyone from v1 to v2 first

    The two-version limit applies to each channel, not to the whole package. As a result, a package that uses channels can have more than two versions across QA, ALPHA and DEFAULT combined. A version has to be added to a channel with MODIFY RELEASE CHANNEL ... ADD VERSION before any directive in that channel can point at it. Patches you create later for that version belong to the same channel automatically.

    Removing a version from a channel takes time. DROP VERSION is asynchronous: the version is fully removed only after every consumer on it has been upgraded to another version. The previous version also stays in the FINALIZING state until the jobs still running on it have finished. If even one consumer's upgrade fails, the old version stays until you fix the cause of that failure.

    This limit exists to keep setup scripts manageable. Because only the previous version can still be live, the setup script for v3 only has to handle upgrades from v2. Patches have no such limit, and any number of patches of a version can be active at once. That is the reason a patch must not change app state, for example by creating tables or adding columns.

    Checkpoint 7 of 11· Match them up

    A release manager hits three different version limits on a package that uses release channels. Match each blocked step to what unblocks it.

    Tap a term, then the definition that fits it.

    Sources216

    5.Default and custom release directives

    A default release directive sets the version and patch that every consumer in the channel gets unless another directive applies to them. A custom release directive has a name and a list of ACCOUNTS, and it pins those accounts to their own version and patch. That is how you give one customer an early fix or hold back an account that is not ready. When both directives apply to an account, the custom one always wins. A listing cannot be published until the package has a default release directive.

    A custom release directive inside the ALPHA channelsql
    ALTER APPLICATION PACKAGE my_app_package
      MODIFY RELEASE CHANNEL ALPHA
      SET RELEASE DIRECTIVE my_custom_release_directive
      VERSION=V1 PATCH=11 ACCOUNTS=(ORG1.ACCOUNT1);

    Changing a directive is the upgrade. When a directive points at a new version or patch, Snowflake queues every instance it covers. Each instance is upgraded when resources become available: Snowflake runs the target's setup script and then its version initializer, if the app defines one. The initializer is an optional step supplied by the app that runs only after the setup script succeeds. If the setup script or the initializer fails, Snowflake calls the previous version's initializer before reporting the failure, so that it can restore resources outside versioned schemas, such as services. MODIFY RELEASE DIRECTIVE changes the version and patch of an existing custom directive, but not its accounts. To change the accounts, you UNSET the directive and SET it again. Run the two steps back to back, because during the gap those accounts fall back to the default directive.

    You can also control when the upgrade starts. Three optional clauses can be added to either kind of directive. Two of them depend on the consumer's maintenance policy, a consumer-controlled setting that defines the consumer's maintenance windows. The provider never sets it; the provider only chooses, with UPGRADE_IN_MAINTENANCE_WINDOW, whether the upgrade respects it.

    Upgrade timing clauses on a release directive
    ClauseEffectRule to remember
    UPGRADE_AFTER = 'timestamp'Earliest time the automated upgrade may begin; consumers can upgrade manually before thenOnly valid while setting VERSION and PATCH; a past timestamp schedules the upgrade immediately
    UPGRADE_IN_MAINTENANCE_WINDOW = TRUEDelays the upgrade to the consumer's next maintenance windowRequires UPGRADE_DEADLINE; cannot be combined with UPGRADE_AFTER
    UPGRADE_DEADLINE = 'timestamp'After this time the app is upgraded regardless of the consumer's maintenance policyLeave consumers enough maintenance windows before it

    Consumers do not have to wait for the queue: ALTER APPLICATION <name> UPGRADE upgrades an app straight away, but only until the automated upgrade has started on it. On packages without release channels, the legacy syntax SET DEFAULT RELEASE DIRECTIVE and SET RELEASE DIRECTIVE work directly on the package, with no MODIFY RELEASE CHANNEL clause.

    Checkpoint 8 of 11· Fill the gap

    A provider needs to move the custom release directive my_custom_release_directive in ALPHA to a different account, ORG1.ACCOUNT1, at V1 patch 11. They have just removed the old directive with UNSET RELEASE DIRECTIVE. To keep the gap as short as possible, which keyword completes the command they should run next?

    ALTER APPLICATION PACKAGE my_app_package
      MODIFY RELEASE CHANNEL ALPHA
       ?  RELEASE DIRECTIVE my_custom_release_directive
      VERSION=V1 PATCH=11 ACCOUNTS=(ORG1.ACCOUNT1);

    Sources463

    6.What the channel means for pricing and trials

    Pricing depends on the channel an instance was installed from. Instances from DEFAULT use the pricing plan configured on the listing, so DEFAULT is the only channel that bills consumers. Instances from QA and ALPHA are free and never use that plan. The plans themselves are covered in Usage-based and subscription-based pricing plans. Because QA and ALPHA instances are free, a paying customer has to end up on DEFAULT, and a preview build in ALPHA does not earn anything.

    Channels also limit how many instances a consumer can install. When MULTIPLE_INSTANCES is enabled, a consumer can install several instances from QA or ALPHA. From DEFAULT on a paid listing, a consumer can have only one instance. On a free listing, multiple DEFAULT instances are still allowed.

    Trials work differently by channel as well, and the outcome turns on the listing type. The two trial-capable types are the limited-trial listing and the paid listing with a trial. On either, a DEFAULT instance is disabled when the trial ends. To keep using the app, the consumer accepts an offer and selects the app from DEFAULT. A QA or ALPHA instance from a limited-trial listing is free and is disabled when the trial ends. A QA or ALPHA instance from a paid listing behaves differently: it stays available after the trial, still free because it never uses the listing's pricing plan. A provider who wants to cut off that access removes the consumer from the channel's active targets.

    Checkpoint 9 of 11· Check yourself

    On a paid listing that offers a trial, a consumer installed the app from the ALPHA channel. The trial period has now ended and the consumer has not accepted an offer. What happens to that ALPHA instance?

    Sources2

    7.Reaching consumers in remote regions with auto-fulfillment

    Consumers in other regions are served through Cross-Cloud Auto-Fulfillment. For them, a directive change does nothing until the application package has been replicated to their region. Whether that happens immediately depends on the LISTING_AUTO_REFRESH property of the package. With the default TRUE, Snowflake starts replication to every remote region whenever a release directive changes, without waiting for the schedule. With FALSE, the change waits for the next scheduled refresh, or for an on-demand refresh started with SYSTEM$TRIGGER_LISTING_REFRESH, which you have to run every time.

    The refresh schedule for application packages is set on the account, not on the listing. It is set with ACCOUNTADMIN and applies to every application package the account publishes, so lowering it for one urgent fix speeds up all of them. Listings with shares attached keep their own intervals. In Snowsight, setting up auto-fulfillment for an app listing goes through Region Availability, where you review the interval configured for the account. A shorter interval delivers fixes sooner, but it also increases replication cost.

    Setting the account-wide auto-fulfillment refresh for all application packages to hourlysql
    ALTER ACCOUNT SET LISTING_AUTO_FULFILLMENT_REPLICATION_REFRESH_SCHEDULE = '60 MINUTES'

    Remote regions are upgraded after the primary region. The directive is first replicated to the package in the remote region. When most apps in the primary region have been upgraded, Snowflake signals the remote region to start its own upgrades. The total time therefore depends on the refresh schedule, the number of installed instances and the number of regions. This also explains why a dropped version can stay around for a long time: it remains until consumers in every region have been upgraded off it.

    Checkpoint 10 of 11· Check yourself

    Consumers in two remote regions get an app through Cross-Cloud Auto-Fulfillment. The application package's LISTING_AUTO_REFRESH property has never been changed. The provider moves the DEFAULT channel's default release directive to a new security patch. How does that patch reach the remote consumers?

    Sources27896

    8.Release metadata and consumer usage metrics

    To see the release setup, use SHOW RELEASE CHANNELS IN APPLICATION PACKAGE <name> for the channels defined on the package, and SHOW RELEASE CHANNELS IN LISTING <listing_id> for the channels on a listing. To see what consumers actually run, use the SNOWFLAKE.DATA_SHARING_USAGE schema.

    Where to look for deployed-app metadata and metrics
    QuestionSourceUseful columns
    Which channel, version and patch is each installed instance on?APPLICATION_STATE viewcurrent_release_channel_name, CURRENT_VERSION, CURRENT_PATCH, CURRENT_INSTALLED_ON
    Has the old version finished draining after an upgrade?APPLICATION_STATE viewPREVIOUS_VERSION_STATE (COMPLETE or FINALIZING)
    How much does each consumer use the app per day?PROVIDER_APPLICATION_DAILY_USAGE_HISTORY viewUSAGE_DATE, CREDITS_USED, CREDITS_USED_BREAKDOWN, STORAGE_BYTES

    Use APPLICATION_STATE to follow a rollout. PREVIOUS_VERSION_STATE shows FINALIZING while jobs on the old version are still running, and COMPLETE once they have finished. Check it before you try to drop or deregister a version. For apps in remote regions, the view also shows whether replication has delivered the upgrade. If an upgrade is still incomplete more than a day after the first refresh that followed it, the refresh process may have a problem, and the next step is Snowflake Support.

    Both views identify installs by APPLICATION_NAME_HASH, not by the instance name the consumer chose. A consumer who reports a problem can run SYSTEM$GET_HASH_FOR_APPLICATION and send you the result. You then match that hash to the instance's channel and version in APPLICATION_STATE and to its daily credit and storage usage in PROVIDER_APPLICATION_DAILY_USAGE_HISTORY.

    Checkpoint 11 of 11· Match them up

    During a rollout, a release manager needs four different pieces of release information. Match each question to the place that answers it.

    Tap a term, then the definition that fits it.

    Sources210116

    Sources

    (11)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “Apps published using this release channel must be targeted to one or more specific accounts within that organization”
      ↩︎ Three release channels for three audiences
      “Versions and patches of an app assigned to this release channel can be published to consumers outside the provider’s organization.”
      ↩︎ Three release channels for three audiences
      “This release channel is the production release channel.”
      ↩︎ Three release channels for three audiences
      “if a version assigned to this release channel fails the security scan, it can no longer be used.”
      ↩︎ Three release channels for three audiences
      “Each version and patch must have its own manifest file and setup script.”
      ↩︎ Versions, patches and the stage path behind them
      “Unlike versions, patches should only contain small updates such as security fixes.”
      ↩︎ Versions, patches and the stage path behind them
      “If no patch number is provided, Snowflake automatically increments the patch version by 1.”
      ↩︎ Versions, patches and the stage path behind them
      “The two-version limit applies to each release channel instead of per application package.”
      ↩︎ The two-version limits on assignment
    2. 2.
      “After release channels are enabled for an application package, they cannot be disabled.”
      ↩︎ Three release channels for three audiences
      “By default, only the DEFAULT release channel is available to all consumers”
      ↩︎ Three release channels for three audiences
      “Apps installed from the QA or ALPHA release channels are meant for testing. Only apps installed from the DEFAULT release channel are meant for production.”
      ↩︎ Three release channels for three audiences
      “All app instances installed using the DEFAULT release channel use the pricing plan configured for the listing.”
      ↩︎ Three release channels for three audiences
      “App instances installed from ALPHA and QA release channels are free and do not use the pricing plan configured for the listing.”
      ↩︎ Three release channels for three audiences
      “To use release channels, you must use a role that has been granted the MANAGE RELEASES privilege.”
      ↩︎ Privileges for release management
      “The ADD VERSION USING '@stage/path' clause of the ALTER APPLICATION PACKAGE command is not supported for application packages that have release channels enabled.”
      ↩︎ Versions, patches and the stage path behind them
      “A release channel can only contain two simultaneous versions.”
      ↩︎ The two-version limits on assignment
      “There is a maximum of two unassigned versions (not added to any release channels) allowed in the application package.”
      ↩︎ The two-version limits on assignment
      “Dropping a version from a release channel is asynchronous and will only be truly dropped once all consumers have been upgraded off that version.”
      ↩︎ The two-version limits on assignment
      “App instances installed from ALPHA and QA release channels are free and do not use the pricing plan configured for the listing.”
      ↩︎ What the channel means for pricing and trials
      “a consumer can only have one instance of an app using the DEFAULT release channel”
      ↩︎ What the channel means for pricing and trials
      “If these apps are installed from a paid listing, they will still be available to the consumer after the trial period ends.”
      ↩︎ What the channel means for pricing and trials
      “they can do so by removing the consumer from the active targets of the release channel.”
      ↩︎ What the channel means for pricing and trials
      “a change to a release directive takes effect in a remote region only after the application package is replicated to that region.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
      “When LISTING_AUTO_REFRESH is FALSE, changes require a scheduled or on-demand refresh.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
      “view the current_release_channel_name column of the SNOWFLAKE.DATA_SHARING_USAGE.APPLICATION_STATE view.”
      ↩︎ Release metadata and consumer usage metrics
      “When release channels are enabled for an application package, each channel has its own release directive.”
      ↩︎ Key concept
      “Adding a version to the QA release channel does not initiate the automated security scan.”
      ↩︎ Exam trap 1
      “App instances installed from ALPHA and QA release channels are free and do not use the pricing plan configured for the listing.”
      ↩︎ Exam trap 4
      “Dropping a version from a release channel is asynchronous and will only be truly dropped once all consumers have been upgraded off that version.”
      ↩︎ Exam trap 5
      “Adding a version to the QA release channel does not initiate the automated security scan.”
      ↩︎ Prediction
      “To create a new version in an application package that already has two versions, providers must deregister an old version.”
      ↩︎ Checkpoint
      “When the application package property LISTING_AUTO_REFRESH is TRUE (the default), Snowflake initiates replication to all remote regions whenever a release directive changes”
      ↩︎ Checkpoint
      “To view the release channels for all installed instances of an app, view the current_release_channel_name column of the SNOWFLAKE.DATA_SHARING_USAGE.APPLICATION_STATE view.”
      ↩︎ Checkpoint
    3. 3.
      “Replaces the entire list of consumer accounts for the release channel with the specified accounts.”
      ↩︎ Three release channels for three audiences
      “Global privilege that allows modifying release channels and release directives on any application package.”
      ↩︎ Privileges for release management
      “Registers a new version in the application package using the files in the stage path specified by path_to_version_directory.”
      ↩︎ Versions, patches and the stage path behind them
      “A version can only be deregistered when it is not assigned to any release channel and no installed application instances are running on it.”
      ↩︎ Versions, patches and the stage path behind them
      “When this parameter is set to TRUE, the UPGRADE_DEADLINE parameter is required.”
      ↩︎ Default and custom release directives
      “the upgrade is delayed until the consumer’s next maintenance window or until the upgrade deadline is reached”
      ↩︎ Default and custom release directives
      “You can’t set the UPGRADE_AFTER and UPGRADE_IN_MAINTENANCE_WINDOW parameters at the same time.”
      ↩︎ Exam trap 3
    4. 4.
      “To set a release directive, a provider must have the MANAGE RELEASES privilege or ownership of the application package.”
      ↩︎ Privileges for release management
      “If you specify both a default and custom release directive, the custom release directive always takes precedence.”
      ↩︎ Default and custom release directives
      “You must define a default release directive in an application package before you can publish a listing”
      ↩︎ Default and custom release directives
      “If you don’t, the installed apps for the accounts assigned to the custom release directive revert to default release directive.”
      ↩︎ Default and custom release directives
      “However, you cannot modify the accounts associated with the release directive.”
      ↩︎ Default and custom release directives
      “If you specify both a default and custom release directive, the custom release directive always takes precedence.”
      ↩︎ Exam trap 2
    5. 5.
    6. 6.
      “Snowflake ensures that only the previous version of the app is active.”
      ↩︎ The two-version limits on assignment
      “the Snowflake Native App Framework does not enforce any restrictions on the number of active patches running.”
      ↩︎ The two-version limits on assignment
      “If a single upgrade fails, providers must fix the reason for the upgrade failure before they can remove the version.”
      ↩︎ The two-version limits on assignment
      “It doesn’t target accounts assigned to a custom release directive.”
      ↩︎ Default and custom release directives
      “If the app defines a version initializer, Snowflake calls it after the setup script succeeds.”
      ↩︎ Default and custom release directives
      “If the setup script or target version’s initializer fails, Snowflake calls the previous version’s initializer before reporting the upgrade failure.”
      ↩︎ Default and custom release directives
      “You can only use the UPGRADE_AFTER clause if you are setting the version and patch.”
      ↩︎ Default and custom release directives
      “If the timestamp has already passed the upgrade is immediately scheduled.”
      ↩︎ Default and custom release directives
      “After the upgrade process begins on an app, consumers can no longer manually upgrade the app.”
      ↩︎ Default and custom release directives
      “Reducing the refresh frequency can increase the costs associated with replication.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
      “When most of the apps in the primary region have been upgraded, Snowflake sends messages to the remote region to begin the app upgrade.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
      “If the upgrade is not complete more than one day after the first refresh following the upgrade”
      ↩︎ Release metadata and consumer usage metrics
      “The previous version remains in the FINALIZING state until jobs that use the previous version finish.”
      ↩︎ Release metadata and consumer usage metrics
    7. 7.
      “When you do this, you update the auto-fulfillment refresh interval for every application package published by your account.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
    8. 8.
      “providers must run this function each time the application package needs to be refreshed.”
      ↩︎ Reaching consumers in remote regions with auto-fulfillment
    9. 10.
      “CURRENT_VERSION | VARCHAR | The current version of the app.”
      ↩︎ Release metadata and consumer usage metrics
      “Possible values are COMPLETE and FINALIZING.”
      ↩︎ Release metadata and consumer usage metrics
    10. 11.
      “Use this view to analyze the daily credit and storage usage for each consumer account of your Snowflake Native App listings.”
      ↩︎ Release metadata and consumer usage metrics

    Ready to test yourself?

    Practise the 35 questions on this subdomain.

    Spotted a mistake, or was something unclear? Tell us.