When you test a data action to troubleshoot issues, you receive additional log output that helps in debugging the Functions. From the test log output, you can obtain the following details:

• Verify that the Function configuration uses the specified settings.
• Verify that the uploaded ZIP file package is the current version.
• Check the debug logs returned from the last 4 KB of the Function output.

For more information, see About the Genesys Cloud Function data actions integration.

• Can I use Genesys Cloud data actions to perform actions on conversations?
• How does Genesys Cloud handle credentials?
• Data action does not appear in Genesys Cloud applications
• Data action fails during testing
• Data action fails in interaction flows
• Data action that uses spaces or special characters fails

For more information about the integration, see About the Genesys Cloud data actions integration.

• Data action does not appear in Genesys Cloud applications
• Data action fails during testing
• Data action fails in interaction flows
• Data action returns a 400 error
• Data action returns a 401 error
• Data action returns a 403 error
• Data action returns a 500 error
• Data action that uses spaces or special characters fails
• executionId in error responses
• Unable to connect to Google

For more information, see About the Google data actions integration.

• Data action does not appear in Genesys Cloud applications
• Data action fails during testing
• Data action fails in interaction flows
• Data action that uses spaces or special characters fails
• Unable to connect to Microsoft Dynamics 365

For more information about the integration, see About the Microsoft Dynamics 365 data actions integration.

• Data action does not appear in Genesys Cloud applications
• Data action fails during testing
• Data action fails in interaction flows
• Data action that uses spaces or special characters fails
• Unable to connect to Salesforce

For more information about the integration, see About the Salesforce data actions integration.

• Custom action fails for unexpected reason
• Data action does not appear in Genesys Cloud applications
• Data action returns a 400 error
• Data action returns a 500 error
• Data action fails during testing
• Data action fails in interaction flows
• Data action that uses spaces or special characters fails

For more information about the integration, see About the web services data actions integration.

• Data action does not appear in Genesys Cloud applications
• Data action fails during testing
• Data action fails in interaction flows
• Data action that uses spaces or special characters fails
• Unable to connect to Zendesk

For more information about the integration, see About the Zendesk data actions integration.