Skip to content
Phinite Docs

Agent Graph Publishing & Versioning

Publishing overview

Section titled “Publishing overview”

Agent Graph publishing in Phinite provides enterprise-grade deployment capabilities with full version control, access management, and observability. Understanding the publishing process is crucial for maintaining stable, secure, and auditable workflows.

Publishing workflow

Section titled “Publishing workflow”
graph TD
    A[Draft Agent Graph] --> B[Save Agent Graph]
    B --> C[Validation Check]
    C --> D{Validation Pass?}
    D -->|No| E[Fix Issues]
    E --> C
    D -->|Yes| F[Add Version Notes]
    F --> G[Publish to Environment]
    G --> H[Version Created]
    H --> I[Deployment Complete]

Access control and permissions

Section titled “Access control and permissions”

Role-based publishing permissions

Section titled “Role-based publishing permissions”
Role Can Save Agent Graphs Can Publish to Dev Can Publish to UAT Can Publish to Prod
SuperAdmin ✅ ✅ ✅ ✅
Admin ✅ ✅ ✅ ✅
Developer ✅ ✅ ❌ ❌
Tester ❌ ❌ ❌ ❌
Viewer ❌ ❌ ❌ ❌

Environment-specific access

Section titled “Environment-specific access”
  • Development: All users with “Developer” role or higher
  • UAT: Requires “Admin” role for publishing
  • Production: Requires “Admin” or “SuperAdmin” role with additional approval workflows

Pre-publishing checklist

Section titled “Pre-publishing checklist”

Agent Graph validation requirements

Section titled “Agent Graph validation requirements”

Common validation failures

Section titled “Common validation failures”

Missing required fields Error: “Please fill all required details for the following nodes: agent, tool”

Debugging steps:

  1. Check each node in the Inspector panel
  2. Verify all required fields are populated
  3. Look for red validation indicators

Resolution: Fill all required fields and re-validate

Invalid connections Error: “Agent Graph contains invalid connections or orphaned nodes”

Debugging steps:

  1. Check for nodes without proper connections
  2. Verify Start node has outgoing connections (Max one)
  3. Ensure End nodes have incoming connections
  4. Look for disconnected nodes in the canvas (Except the child nodes)

Resolution: Connect all nodes properly and ensure graph integrity

Tool integration errors Error: “Tool integration failed validation”

Debugging steps:

  1. Verify API keys and credentials
  2. Review tool parameter mapping

Resolution: Fix tool configuration and authentication

Publishing process

Section titled “Publishing process”

Publish Pn

Step-by-step publishing

Section titled “Step-by-step publishing”

  1. Save your flow Click “Save” in the studio header to persist your changes.

  2. Run validation The system automatically validates your flow before publishing.

  3. Add version details Provide a clear description of changes in this version.

    Good version notes:

    Version 2.1.0 - Customer Service Agent Graph
    - Added RAG integration for policy knowledge
    - Improved error handling for payment failures
    - Updated email templates for better customer experience
    - Fixed issue with order lookup timeout

    Poor version notes:

    Updated stuff

  4. Select target environment Choose the appropriate environment for deployment.

  5. Confirm and publish Review all settings and confirm the publication.

Version management

Section titled “Version management”

Version history interface

Section titled “Version history interface”

The version history panel provides comprehensive version management:

  • Version list: View all published versions with timestamps and notes
  • Version details: Inspect specific version configurations
  • Copy to draft: Create a new draft based on any published version
  • Environment status: See which environments each version is deployed to

Version numbering

Section titled “Version numbering”

Phinite automatically manages version numbers:

  • First published version: Starts at version 1
  • Subsequent versions: Incrementally numbered (2, 3, 4, etc.)
  • Draft versions: Not numbered until published (default 0)
  • Version notes: Required for all published versions

Copying versions to draft

Section titled “Copying versions to draft”

  1. Access version history Click “Version History” in the studio sidebar.

  2. Select source version Choose the version you want to copy from the list.

  3. Copy to draft Click “Copy to Draft” and confirm the action.

  4. Edit and republish Make your changes and publish as a new version.

Post-publishing monitoring

Section titled “Post-publishing monitoring”

Build verification

Section titled “Build verification”

  1. Check Build with particular agent graph version Verify the agent graph is connected to target build and build is connected to the desired environment.

  2. Test flow execution Run test scenarios to ensure the flow works as expected.

  3. Monitor performance Use Observability tools to track flow performance.

  4. Review logs Check execution logs for any issues or errors.

Performance monitoring

Section titled “Performance monitoring”
  • Execution success rate: Track how often flows complete successfully
  • Response times: Monitor flow execution duration
  • Error rates: Identify common failure points. Work on prompt or changing models.
  • Resource usage: Track token consumption and API calls

Best practices

Section titled “Best practices”

Version management

Section titled “Version management”
  • Descriptive notes: Always provide clear, actionable version descriptions
  • Incremental changes: Make small, focused changes rather than large overhauls
  • Testing: Thoroughly test flows before publishing to production
  • Rollback plan: Keep previous versions available for quick rollback

Security considerations

Section titled “Security considerations”
  • Access control: Regularly review who has publishing permissions
  • Environment isolation: Maintain strict separation between environments
  • Audit trails: Monitor all publishing activities for compliance
  • Secret management: Ensure sensitive data is properly secured

Performance optimization

Section titled “Performance optimization”
  • Efficient flows: Design flows for optimal performance and resource usage
  • Monitoring: Set up alerts for performance degradation
  • Scaling: Plan for increased load and usage patterns
  • Optimization: Continuously optimize based on performance data

Expose as an A2A agent (Agent Registry)

Section titled “Expose as an A2A agent (Agent Registry)”

After you publish an agent graph, you can register it in the Agent Registry so other systems and agents can call it over the A2A protocol.

  1. Publish the agent graph Complete validation and publish at least one version to your target environment. Unpublished graphs cannot be exposed.

  2. Open Configure Agent In Graph Studio (local/dev environments), click Configure Agent in the canvas header, then Create New Build in the Expose modal.

  3. Complete the Expose wizard Fill in Agent Build Config, optional export settings, and the Agent Card (skills, tags, visibility). Submit with Attach Agent Card.

  4. Promote when ready New builds start as test. Promote to live from Agent Cards when production routing is approved.

Full wizard details: Expose your agent graph. Hosted URL patterns: Endpoints & lifecycle.

Integration with other components

Section titled “Integration with other components”

Assistant integration

Section titled “Assistant integration”

Observability integration

Section titled “Observability integration”

Environment management

Section titled “Environment management”