Expose executing Function name, ID, and snapshot/version through Function Info

Please expose system-generated runtime metadata within Tulip Function logic through the Function Info datasource:

  • Function Name

  • Function ID

  • Executing Version / Snapshot ID

  • Reference Type: Development or Snapshot

These values should be available in expressions, table-write actions, and Function outputs.

Problem

We are investigating duplicate Functions and apps remaining linked to older Function snapshots after imports or restores. We need to identify exactly which Function and version executes when an app calls it.

Manually creating “Function Name” and “Version” variables is not reliable:

  • Duplicated Functions inherit those values and can incorrectly identify themselves as the original.

  • Manually maintained revision labels can get out of sync.

  • Values passed by the calling app describe what it expects to execute, not necessarily what actually executes.

Use case

We want to log this metadata to a Tulip Table alongside the calling app, app version, step, and execution timestamp. This would allow us to:

  • Identify calls using unintended duplicate Functions.

  • Detect outdated snapshot references.

  • Verify that apps execute their approved Function versions.

  • Include accurate Function identity and version details in error messages.

  • Troubleshoot migrations through Dev → Validation → Production.

Snapshots are appropriate for preserving validated logic. The goal is not to eliminate snapshots or force every app onto the latest version, but to make the executing version identifiable and verifiable.

Expected behavior

The metadata must come from the Function and version actually executing, without manually maintained variables or caller-supplied identifiers.

For example:

  • A duplicate reports its own Function ID.

  • A snapshot reports its own executing snapshot ID, not the latest development version.

  • The reference type clearly distinguishes Development from Snapshot.

This would complement native execution logging while allowing customers to build targeted diagnostics using existing Tulip Tables and Function logic.

1 Like