Skip to main content

End of Life Insights FAQ

With the 2024.1 release, the Insight tool* has reached end of life and is no longer available in Alteryx Server.

What can you expect to happen with assets that contain Insights? How will this change impact other functionality within Server? To give you answers to the most common questions, we have prepared this document.

*This is specific to the Insight tool and not the Business Insights Data Product.

FAQs

1. What happens to my Insights when I upgrade to 2024.1?

The removal of Insights in 2024.1 should not affect the upgrade process. The service should start without any errors and all workflows including those with Insights should be visible in Server UI. However, any Insight will no longer be rendered in Server UI.

2. What happens to schedules that are using a workflow that has an Insight?

Schedules containing Insights will continue to run successfully. There will be no impact on the designated date and time of when the schedule should run.

3. What should I expect from workflows that have been shared with me containing Insights?

All assets containing Insights that are shared via a collection will continue to behave in the same way as assets without Insights. However, no Insights will be rendered in Server UI.

4. What happens if I run an Analytic App that has an Insight as an output?

Apps containing Insights will continue to execute successfully. However, no Insights will be rendered as an output of the app.

5. What happens if I save a Macro with an Insight on Server 2024.1?

All macro functionality will remain the same on Server 2024.1.

6. What happens if I directly access http://{my_url}/gallery/#!/insights?

Directly accessing that URL will result in a PAGE_NOT_FOUND error.

7. What happens if I try to upload an Insight from an older version of Designer (2023.2 or older) to Server 2024.1?

You will be able to publish a workflow containing an Insight from an older version of Designer to Server 2024.1. The workflow will successfully run on Server, however the Insight will not render in Server UI.

8. What happens when I transfer an asset with an attached Insight?

When transferring ownership of an asset that contains Insights, no Insight related errors should occur. The transfer should run successfully for both workflows and schedules.

9. Can I still use API endpoints related to Insights?

No, all API endpoints related to Insights are disabled in Server 2024.1. Please see list of affected endpoints below:

  • GET /webapi/admin/v1/insight

  • GET /webapi/admin/v2/insights

  • POST /webapi/v3/collections/{collectionId}/insights

  • POST /insights/{insightId}_dash-update-component

  • DELETE /webapi/v3/collections/{collectionId}/insights/{insightId}

For the GET /webapi/v3/users/{userId}/assets endpoint, if assetType=Insights, this will return the default response when the asset type cannot be interpreted, which is to return all asset types.

10. What happens if I upload an asset (workflow, app, macro) containing an Insight via the current APIs Server 2024.1?

The workflow will be published and will continue to run on the Server. However, no Insights will be rendered in Server UI.

11. What happens if I publish a new version of a workflow (with Insights) on top of an existing workflow (without Insights)?

The new version of the workflow would continue to successfully run on Server, however, the Insights will not be rendered in the Server UI.

12. What happens to any Insight related records in my persistence layer?

Any Insight related records will continue to show in the persistence layer.

13. If I migrate to SQL Server, what happens to any Insight related records after the migration?

Any Insight related records will be migrated over to your SQL Server and will continue to remain in your chosen persistence layer.

14. Are there any alternatives to Insights?

Most functionality can be replicated via our Reporting tools in Designer. For more information, about Reporting tools, go to Reporting.

In this section: