Skip to main content

Getting Help

The Serverless Workflow community is here to help! There are several ways to get support depending on your needs.

Community Support Channels

Slack

The fastest way to get help is through our community Slack channel:
  • Join CNCF Slack
  • Navigate to the #serverless-workflow channel
  • Ask your question or describe your issue
Our community members and maintainers actively monitor this channel and typically respond within a few hours during business hours.

GitHub Discussions

For longer-form questions, design discussions, or general inquiries:
  • Visit GitHub Discussions
  • Search existing discussions to see if your question has been answered
  • Create a new discussion if needed
This is ideal for:
  • Architectural questions
  • Feature requests and feedback
  • Use case discussions
  • Community announcements

GitHub Issues

For bug reports, specification issues, or concrete problems:
  • Check existing issues
  • Create a new issue with a clear description of the problem
  • Include relevant details: version, environment, steps to reproduce
Please use issues for:
  • Bug reports
  • Specification clarifications
  • Documentation improvements
  • Concrete feature requests

Weekly Meetings

Join our weekly community meetings to:
  • Ask questions in real-time
  • Present use cases or problems
  • Get direct feedback from maintainers
  • Collaborate with other community members
Meeting Time: Every Thursday at 9:00 AM ET

Mailing Lists

For formal inquiries or announcements:

Documentation Resources

Before asking for help, check our comprehensive documentation:

Commercial Support

While Serverless Workflow is an open-source project, several organizations offer commercial support, consulting, and training:

Reporting Security Issues

If you discover a security vulnerability:
  • DO NOT open a public GitHub issue
  • Email the maintainers privately at [email protected]
  • Include detailed information about the vulnerability
  • Allow time for the maintainers to address the issue before public disclosure

Code of Conduct Issues

For Code of Conduct violations or concerns:

Contributing to the Project

The best way to get support is often to contribute to the project:
  • Read our Contributing Guide
  • Fix documentation that you found confusing
  • Improve error messages or examples
  • Help answer questions from other community members
By contributing, you’ll develop deeper knowledge and help make the project better for everyone!

Social Media

Stay updated with announcements and news:

Response Times

Please note that all support is provided by volunteers and community members:
  • Slack: Typically within a few hours during business days
  • GitHub Issues/Discussions: Within 1-3 business days
  • Mailing Lists: Within 1-3 business days
  • Security Issues: Acknowledged within 24-48 hours
For urgent issues, we recommend using Slack or attending the weekly meeting.

Build docs developers (and LLMs) love