Welcome to Next Matter home pagelight logodark logo
  • Contact us
  • Status
  • Sign in
  • Sign in
Get started
Components
Integrations
Portals
Sidebars
Solutions
Updates
APIs
  • Product updates
  • Videos
  • Overview
    • Welcome to Next Matter
    • Product automation
    Build
    • Get started: Build workflows
    • Integrate across tools
    • Visual builder
    • Notes in workflow
    • Branch your workflows
    • Troubleshooting workflows
    Organize
    • Inbox
    • My requests
    • Datasets
    Run
    • Get started: Work with tasks
    • Manage workflows/instances
    • Reassign tasks
    • Complete steps
    • Participate in workflows
    • Create external workflows
    • Complete tasks as guest
    Report
    • Export data
    • Search
    • Monitor data
    • Stages board
    • Monitor progress with roadmap
    Manage your account
    • Personal profile
    • Reset your password
    Manage workspace
    • Users and teams
    • Security and SSO
    • Custom branding
    • Company dashboard
    Build

    Troubleshooting workflows

    Refer to this page if you’ve run into issues creating or starting a workflow.

    Check custom integration steps and verify that the phrase Api-Key is present in the Header.

    1. In the left-hand navigation, click Workflows.
    2. Click the workflow containing the integration step.
    3. Click Settings to edit the step.
    4. Make sure your API key is proceeded by the Api-Key phrase.

    Alternatively, a 401 error might mean that the account connected to an integration step got deactivated or deleted. It might also show if the same account was connected in another environment and then disconnected.

    This might happen when you don’t select Google Slides in the Authorization field in the integration step’s settings.

    This happens if you have selected to skip a failed step. You can configure this in the step’s settings in the On Failure section. Probably the step failed and it was skipped.

    To quickly see what the issue with the step might be, expand the skipped step and right-click to inspect. Next, delete the overlay <div>.

    This might happen when you edit the Body in an external JSON editor and then copy it over to Next Matter. Data references need to be selected directly in Next Matter (by clicking the braces and selecting the value from the dropdown).

    It might be because there are brackets or braces to the variable name. Make sure the name doesn’t contain any brackets or braces.

    If you’re getting this error when clicking Test integration in the Complete step automatically template, it’s because the auto-complete step relies on the instance ID of the running instance. Clicking Test integration in the editor with no running instance will always produce this error even if all placeholders are correct.

    If this happens, try refreshing the screen.

    Your integration test might fail with a Bad gateway or Not authorized error. In such cases, you can take over a step, re-configure it, and retry.

    You can take over a step if you’re a workflow owner or a workflow tech lead.

    It might be because you’ve edited the value that’s used in the condition, and you haven’t updated the condition itself.

    Was this page helpful?

    Branch your workflowsInbox
    youtubelinkedin
    Powered by Mintlify
    Assistant
    Responses are generated using AI and may contain mistakes.