Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
Video Walkthrough
Video chapters:
The following versions have been tested and verified to work with QPI (1.4.0):
Qlik Sense February 2022 to Qlik Sense November 2023.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
After following the Qlik article Configure Qlik Sense to use a dedicated PostgreSQL server and update the connection string to point to the new host, Qlik Sense appears to work fine at first. However, access by the Qlik Sense Service account to the old host is registered or errors are found in the logs similar to what is found in the example below:
In the AppDistributionService trace logs:
307308 20210104T170444.859+01:00 INFO QLIKSERVER 70 DOMAIN\serviceaccountname Retry attempt: 10/10. Previous result: "No such host is known". 304796
307309 20210104T170451.812+01:00 ERROR QLIKSERVER 70 DOMAIN\serviceaccountname Error processing message queue notifications. System.Net.Sockets.SocketException (11001): No such host is known
at System.Net.Dns.HostResolutionEndHelper(IAsyncResult asyncResult)
There are a few new services starting on the September 2019 release of Qlik Sense which did not exist in June 2018. Some of them were also removed/replaced on the new release.
# Set the Installation Directory for Qlik Sense
$installDir = 'C:\Program Files\Qlik\Sense\'
#change that to the new database server
$newdatabasehostname='new database server'
# Specify the new password for the qliksenserepository account
$password = 'MyNewPassword'
# Find all Configure-Service.ps1 scripts in the installation directory and execute them
$files = Get-ChildItem -Path $installDir -Include Configure-Service.ps1 -Recurse
foreach ($file in $files) {
$ScriptToRun=$($file.FullName)
&$ScriptToRun $newdatabasehostname 4432 qliksenserepository $password -postgresHome 'D:\Qlik\Sense\Repository\PostgreSQL\12.5'
}
In case of having a custom path Qlik Sense installation, change the last line to:
&$ScriptToRun $newdatabasehostname 4432 qliksenserepository $password -postgresHome 'D:\Qlik\Sense\Repository\PostgreSQL\12.5'
}
Where "D:\Qlik\Sense" is Qlik Sense installed folder and where "12.5" is the Postgres version installed.
Change to the following directories with the commands below before running the Configure-Service.ps1 command listed further below.
Repeat the step for every subfolder mentioned below.
Note: If you previously upgraded you may find folders in your system which are not listed here. Ignore them. No steps need to be taken.
Qlik Sense February 2021 and later.
Locate Configure-Service.ps1 in C:\program files\Qlik\Sense\.
It lists all services that need to be changed.
Qlik Sense June 2018:
Qlik Sense September 2019:
Example:
For AppDistributionService...
PS C:\> cd 'C:\Program Files\Qlik\Sense\AppDistributionService' PS C:\Program Files\Qlik\Sense\AppDistributionService> .\Configure-Service.ps1 DatabaseHost Databaseport DatabaseUser DatabasePassword
e.g. .\Configure-Service.ps1 newdatabasehostname 4432 qliksenserepository Password123!
The answer will look similar to this:
AppDistributionService configuration started. WARNING: Skiping the database initialization. No superuser or password specified. Reading the settings file. Saving the modified settings. Exporting the copy of the invocation parameters. AppDistributionService configuration successful.
Qlik Replicate's User Interface comes with a set of monitoring tools to help us understand and break down what is happening to the task on all levels. In this article, we will focus on the incoming changes from the CDC (Change Data Capture) process and understand where the changes are and what happens to the changes along the way.
To monitor the incoming changes for the task, we would need to go to the Monitor tab, switch to the Change Processing tab, and click on Incoming Changes.
From this main screen, we see five vertical bars. Here the bars are separated by the following:
The incoming changes are grouped into two categories:
Each category is further broken down into two locations:
Incoming Changes is the total number of changes and transactions that are being read from the source database endpoint. In the picture below, you can see that 12 changes are read from 5 transactions.
The two Accumulating bars are a breakdown of the Incoming Changes. Accumulating means the Replicate server is reading the changes from the source database endpoint.
In the picture below, you will see the values set in the task settings that determine if the incoming changes will go to the In Memory bar or the On Disk bar. In this case, the task has been allocated to use a maximum of 1024MB of memory for the task, and the transaction duration is kept for a maximum of 60 seconds. Changes that exceed this memory limit or transaction duration are held in the On Disk bars.
Incoming changes that are held In Memory bar can be offloaded to the next step where Replicate will begin the apply process. Incoming changes that are held On Disk bar will wait for available memory before they are placed into the In Memory bar.
As a reminder, the total number of changes/transactions in the two Accumulating bars will be equal to the Incoming Changes bar. The two Accumulating bars are just a breakdown of where the changes are currently stored. They are either in memory or on disk waiting for memory to start the processing.
The next step of the process is the two Applying bars. Applying means the Replicate server is gathering the changes on the Replicate server while it waits until the task settings have been reached and the batch of changes are applied to the target database endpoint.
Please refer to the Change Processing Tuning values you have set in the task settings to determine the wait time for the Replicate server before the batch of changes is applied to the target database.
In the picture below, you will see that the task has been set to move a batch of changes to the apply process when a duration of 1-30 seconds has elapsed or the batch of changes has reached 500MB in size. Note that these are just the default values and are by no means the exact value you should set for the task.
The In Memory and On Disk bars work the same way as the previous set of In Memory and On Disk bars. Up to 1024MB of memory can be used for the task before changes are stored on disk. As memory is freed up from changes being applied to the target, the changes will be moved from the On Disk bar to the In Memory bar which is then applied to the target in the next batch of changes.
When are changes captured from the source?
Changes are captured when the task is in a running state. The task will have a green circle with a white triangle icon. The task can also be in a stopped state with a grey circle and white square icon or an error state with a red circle and white X icon. The Stopped and Error state tasks will not capture changes anymore.
What happens to the changes when I stop the task in midst of the replication process?
Replicate will immediately stop capturing any more changes from the source database. Replicate will continue to apply changes to the target database for up to 30 minutes. After 30 minutes have passed, any remaining changes will be left in the Applying - On Disk bar. This means that changes are stored on the Replicate server disk. The remaining changes will be applied the next time the task is resumed.
What happens to the changes stored on the Replicate server disk if I choose to use the advanced run options to start the task from a timestamp instead of resuming the task?
If the "Start from a timestamp" option is used instead of the "Resume" option, all changes that are still stored on the Replicate server disk will be deleted. Replicate will start reading changes again from the chosen timestamp.
Will Replicate know which changes have not been applied to the target database or is there a chance Replicate will read the same changes twice?
Replicate uses an internal variable called stream position to keep track of changes that have been read. The stream position consists of the record position within the source database which lets Replicate know the exact location of the last change read. The stream position also lets Replicate know the exact record position that has been applied to the target. This allows Replicate to stop and resume without duplicating any source reads or target apply processes.
If I use the same source endpoint in another task, will the incoming changes count CDC from the other task too?
No, the monitoring tool UI that you see for the task only contains information pertaining to the single task you are viewing. Each task has its own separate set of information regarding the changes for the task.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This is a companion article to Qlik Sense Enterprise for Windows - New Security Patches Available Now and only applies to the patches affected by QB-30633.
If you have experienced issues with visualizations and extensions not loading after upgrading to the security patches released on the 4th of December 2024, upgrade to the new patches which address QB-30633:
If visualizations and extensions do not behave as expected after the upgrade, follow the outlined steps below:
If the extensions are not available in the Qlik Sense Management Console, on the file share, as well as in the assets panel
Solution:
Restart the Qlik Sense Services services, then verify again
If the extensions are available in the Qlik Sense Management Console, on the file share, as well as in the assets panel, but not visible in any of your Qlik Sense apps
Solution:
Clear the browser cache
If sheets are not rendering and the error 'an error occured' is thrown
Solution:
Clear the browser cache
If issues continue regardless, contact support so that we can assist you effectively.
This document explains how to manually setup custom connectors within Qlik Sense with Standard mode without legacy mode. More info under Legacy vs. Standard Mode in Qlik Sense: Explainer and Security Considerations
Pre-requisites:
After installing Qlik SAP Connectors on a Qlik Sense Enterprise Server, some connectors like Qlik SAP Report Connector, Qlik SAP Query Connector..., are not automatically installed. Thus, when migrating from a "QlikView environment" to "Qlik Sense Enterprise", those specific connectors need to be manually set in Qlik Sense.
Step 1:
After successful connection, click Create button
Step 2:
Step 3:
It should look like:
Step 4:
Step 4:
Optional Steps:
With the latest versions of QlikView and Qlik SAP Connector, you don't need to perform this step.
You can access Qlik Sense demo apps from https://demos.qlik.com/.
If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.
If you are looking to download demo apps:
After a Qlik Sense upgrade, the Qlik Sense Repository service fails to start. The following error is logged in the Windows Application Event log:
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5'
at Repository.QRSService.Start(Action`1 terminate)
at
The initial recommendation is to repair the installation. See How to repair an installation.
If the repair does not resolve the problem:
The Qlik.Sense.Logging.dll present in [Installation Qlik Sense folder]\Repository\ was missing required inforamtion.
Affected versions:
CVE-2024-7348 is a Time-of-Check Time-of-Use (TOCTOU) race condition vulnerability in pg_dump, a utility used for backing up PostgreSQL databases. This vulnerability allows an attacker to replace a relation type (such as a table or sequence) with a view or foreign table right when pg_dump is running. Because pg_dump often runs with superuser privileges, this attack could execute arbitrary SQL code, leading to unauthorized actions or data corruption. Source: https://www.postgresql.org/support/security/CVE-2024-7348/
Qlik can confirm that pg_dump is not actively used in the Qlik Sense Enterprise on Windows code.
Both steps are required to fully mitigate the issue.
Always verify compatibility between your Qlik Sense version and PostgreSQL before planning an upgrade.
QPI does not utilise pgdump.exe.
Upgrading Qlik Sense Enterprise on Windows fails with a generic error message:
An error has occurred
For detailed information see the log file
The Qlik Sense Repository Database service is no longer installed after the failed installation.
This means that the database password validation did not complete and a partial rollback has occurred. This has removed the database software, but it has not removed the database itself.
The database password is normally password is checked before the upgrade process begins, but under some circumstances, such as the database service being stopped, this check does not occur. Once the new version of the database software is installed it will attempt to open the database as part of the install verification process and will fail. This then prompts a rollback of the database software and removing the new version.
Reinstall Qlik Sense. (Uninstall, Reinstall)
During the uninstall process, do not remove the certificates or database.
Once Qlik Sense is uninstalled, you can proceed to install the desired upgraded version of Qlik Sense, the installer will detect the existing database and request the password, if it is from an earlier version the installer will make the necessary changes as part of the installation process.
When using context or global map to pass values to subjobs or other child jobs components, the record passing is showing data inconsistency issue under multi-thread scenarios.
Considering the various factors, you need to choose a Thread Safe and Mutable Object. In this case, try to create a ConcurrentHashMap (which is an implementation of Map) as a single Object that can be passed to all child Jobs or other components and it can also accept parameters we want to add. In fact, this provides similar functions to the globalMap, but the globalMap has no thread-safe guarantee.
globalMap.put("sharedMap", new java.util.concurrent.ConcurrentHashMap());
((java.util.Map) globalMap.get("sharedMap")).put("firstname","xxx");
System.out.println("firstname=" + ((String) ((java.util.Map) globalMap.get("sharedMap")).get("firstName")));
When you connect to the Qlik Sense Enterprise on Windows hub or the Qlik Cloud Analytics hub with Firefox and open an app, the browser automatically shows a window suggesting a translation from Greek to the OS/Qlik language, as shown in this image.
The suggestion provided by Firefox can be ignored by clicking Cancel.
This has no impact on the functioning of Qlik.
The message is shown by Firefox, which can incorrectly detect Greek language contents in Qlik apps. The problem has been reported to Firefox developers.
QB-29728
This article explains how to simply set up JWT authentication using Qlik Sense default certificates and test it.
Click here for Video Transcript
In order to integrate your solution with Qlik Sense using JWT authentication, you will need to pass in your code the JWT token in the authorization token for the first request to Qlik Sense so that a session is created.
The following error is showing when executing a job on Talend Administration Center from MetaServletCaller.bat
{"errorStatus":"CONNECTION_TO_SERVER_FAILED","execBasicStatus":"UNKNOWN","execDetailedStatus":"UNKNOWN","execDetailedStatusLabel":"Unknown, JobServer might be unreachable","execRequestId":"****","executionTime":{"millis":4817930,"seconds":4817},"returnCode":0,"status":"UNKNOWN"}
When considering upgrades, please upgrade your Job Server to the same version as the Talend Administration Center's, since Talend Administration Center and Job Server will interact with each other in work and installing an old version from one of these two applications may cause issues
Internal Jira case TAC-19340
This article explains how the Qlik Sense app button component can be used to send custom parameters directly to the automation without requiring a temporary bookmark. This can be useful when creating a writeback solution on a big app as creating and applying bookmarks could take a bit longer for big apps which adds delays to the solution. More information on the native writeback solution can be found here: How to build a native write back solution.
Contents
Environment
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
When running the Job that includes a tFTPConnection component, the following error occurs:
Error: Exception in component tFTPConnection_1 com.jcraft.jsch.JSchException: Algorithm negotiation fail.
The dependent JSCH jar 0.2.18 is missing.
To resolve this issue, kindly follow these steps:
QlikView and Qlik Sense provides the capability to extend presentation capability by creating extension objects.
It is important to note that Qlik only supports the API calls made to the QlikView or Qlik Sense server. Qlik does not directly support 3rd party extension implementations. For issues with 3rd party provided extensions, the primary support channel is the 3rd party extension provider.
For Qlik to support API-related issues, the script or code must be minimised to show the issue is related to the specific API and not the custom code using the API. This initial troubleshooting and simplification of the script must be done by the extension developer.
Extensions provided by Qlik employees on Qlik Community are not supported by Qlik. These extension solutions are supported within these communities.
Extensions developed by Qlik’s partners, including certified Extensions, are supported by the Qlik partner.
A customer should also consider this:
Talend Remote Engine Heart Beat is failing hourly with 'GOAWAY received' error and the karaf.log shows below:
2024-08-01T10:16:58,638 | ERROR | pool-28-thread-1 | JAXRSUtils | 469 - org.apache.cxf.cxf-rt-frontend-jaxrs - 3.6.2 | | Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
2024-08-01T10:16:58,638 | WARN | pool-28-thread-1 | PhaseInterceptorChain | 467 - org.apache.cxf.cxf-core - 3.6.2 | | Interceptor for {http://pairing.rt.ipaas.talend.org/}PairingService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
Caused by: java.io.IOException: /<IP>:<port>: GOAWAY received
heartbeat.interval=60 (by default)
with heartbeat.interval=65
Do not set heart interval to more than 180 seconds(3 mins). If Talend Cloud does not receive a heartbeat from the Remote Engine for more than 3 mins, it will show the Remote Engine's status as unavailable.
It seems that the connection to the server pair.xx.cloud.talend.com is kept during 60 seconds and Heartbeat.interval > 60 seconds allows to close this connection and prevent "GOAWAY received" error message.
For more information about heartbeat concept and heartbeat interval, please refer to documentation:
Monitoring-remote-engine-health
Internal Jira Case ID: TMC-4122
When attempting to add the Job in TAC via the Normal task, after selecting the branch, the system continuously loads and subsequently encounters the following error:
"Operation failed: https://github.com/talendjob: git-upload-pack not permitted on 'https://github.com/talendjob/' -- For more information see your log file."
Using one Functional SSO (FSSO) and password to login to GitHub.
GitHub has changed its authentication policies and now uses tokens instead of passwords. Please refer to the link below for more information:
https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/
To configure GitHub with a token and then configure the same in TAC, please follow the instructions provided in the link below: https://community.qlik.com/t5/Official-Support-Articles/Talend-Cloud-Two-Factor-Authentication-using-personal-access/ta-p/2151788.
Configure GitHub using the token, set it up in TAC, restart TAC, and attempt to create a new task.