Troubleshoot workflows

When a step returns a large amount of data, the Output tab shows a message like results <data (6971239 bytes)> instead of the full result. The byte count varies with the size of the data.

Your data was retrieved successfully. The Output tab just doesn't render a result once it gets past a certain size.

This depends on the total amount of data, not the number of items. A list of 100 items can trigger the message if each item carries a lot of data, such as assets that include all their software and vulnerabilities.

This is a separate visualization limit. When a step returns a list, the Output tab displays a maximum of 250 items, even if the list contains more.

All the items are still retrieved and passed to your later steps. Only the Output tab's preview is capped at 250.

Both limits mainly get in the way when you're building a reference path to data from another step. Inside a loop, for example, you might not be able to build the path from the Output preview.

• Use the sample output. The message in the Output tab points you to a sample output. Use it to build your reference path. This is the quickest option.
• Limit the records temporarily. If you'd rather build the path from real data, lower the number of records the asset action returns while you work. Use the Max records field on the asset action to cap it.

When you limit the records, set a number that's representative of the workflow you're building. Keep it at or below 250 so the results still show in the Output tab.

The Output tab only shows the first item of a loop. If that first item is missing the field you want to reference, such as a location, you can't build the path by selecting it from the Output.

There are two ways around this:

• Copy the reference path. Open the asset's additional details, copy the reference path for the field you need, and paste it into your step. If the step runs inside a loop, add currentItem to the start of the path.
• Filter to an asset that has the data. Find an asset that has the field you need and copy its asset key from the URL. Then filter by that asset key in a filter action. The first item in the filtered list now has the field, so you can build your path against real data.

Filtering this way also helps when you want to troubleshoot one specific branch. Because the Output tab only shows the first item of a loop, filter to assets you know will follow the branch you're testing.

If you type a reference path straight into a value field instead of inserting it as a reference, Flow Builder treats it as plain text. A condition then compares the literal path text against your value, so the comparison is always false.

To insert a reference, select the reference control in the field and add your path in the reference section.

A reference comparison includes everything in the field, including trailing spaces and new line characters. Extra whitespace makes an otherwise-correct condition fail. Remove new lines and blank spaces from your reference fields before you compare them.

When you reference an item in a list by its position, the condition breaks as soon as the order changes. A custom field at index 3, for example, won't stay at index 3. The order can differ between assets, and it changes when you add new custom fields.

Filter the list instead:

1. Add a filter action and select your list, such as your custom fields.
2. Filter by the item's key. A custom field key doesn't change for your site unless you delete the custom field and create it again. You can copy the key from the asset action's output.
3. Reference the filtered result at index 0. After filtering, the item you want is the only one in the list, so it's always at index 0.

If the item doesn't exist, the filtered list is empty and the condition fails. That's the expected result.

The Output tab only shows the first item of a loop, so it's limited when you need to inspect later iterations. Add log steps to print the data you care about.

For the first 10 items in a loop, the logs appear in the step's Log tab, beside the Output tab. If your item runs in a later iteration, turn on the Logs toggle in the steps section. The log information then appears on the main Steps screen.

When an action that connects to an external app fails, such as a Slack Post Message action, check the connection first.

1. Confirm the connection is active. The status indicator next to the connection should be green. If it isn't, reconnect.
2. Check the credentials. Verify the client ID, client secret, and signing secret are correct. Wrong values cause the connection to fail.
3. Check the connection logs. The logs and the authorization screen usually show the specific error.
4. Check the redirect URL. A wrong redirect URL is a common cause of a failed connection.
5. Check scopes and permissions. A connection can succeed while the action still fails because a required scope or permission is missing. Open the error on the failed action for hints, such as a Slack scope that isn't configured in the external app.

Saving and testing a workflow doesn't make your changes live. A running workflow keeps using its enabled version until you save a new version and enable it.

After you finish your changes:

1. Save the workflow as a new version.
2. Enable that version. You can do this when you save it (select Enable this version), with the Enable icon next to the workflow name, from the version history tab, or from the 3-dot menu on the Workflows list page.

Once the new version is enabled, the workflow includes your latest changes the next time it runs from its trigger. For more detail, see Enable Workflows.