#I am facing a HTTPS connection error while using Jira Composio actions

1 messages · Page 1 of 1 (latest)

supple timber
#

{'data': {}, 'error': 'HTTPSConnectionPool(host='your%20your-domain.atlassian.net', port=443): Max retries exceeded with url: /rest/api/3/project (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7fee5f4337d0>: Failed to resolve 'your%20your-domain.atlassian.net' ([Errno -2] Name or service not known)"))', 'successfull': False, 'successful': False}I'm unable to retrieve the project details at the moment. Could you please provide me with more context or try again later?

#

Here's my code snippet:
from langchain.agents import create_openai_functions_agent, AgentExecutor
from langchain import hub
from langchain_openai import ChatOpenAI
from composio_langchain import ComposioToolSet, Action, App
#from dotenv import load_dotenv
#import os

#load_dotenv()

llm = ChatOpenAI(api_key = "api_key")
prompt = hub.pull("hwchase17/openai-functions-agent")

#api_key="api_key",
#, entity_id="email_id"
composio_toolset = ComposioToolSet(api_key="api_key")
tools = composio_toolset.get_tools(actions=['JIRA_GET_ALL_PROJECTS'])

agent = create_openai_functions_agent(llm, tools, prompt)
agent_executor = AgentExecutor(agent=agent, tools=tools, verbose=True)
task = "give me the name of the project and key whose id is 11021"
result = agent_executor.invoke({"input": task})

flat hearthBOT
#

Hey Mihir, team is taking a look into this, will update soon!

flat hearthBOT
#

are you using oauth2 or api token type of auth?

supple timber
#

Hi Samvit!
Used API token

supple timber
#

@finite merlin As discussed in the call, here's the file with the code snippet we were trying. We are trying to troubleshoot the issue regarding HTTPS Connection and also to bypass using the terminal (wherein we had to run the 'composio add jira' command).
Also, for our case -

  1. since we are using the Jira Service Management Portal our objective here is to use the triggers in order to gather the status of the tickets and accordingly update the ticket ID using the order of the workflow.
  2. Depending on few issue types, we need to, for some issue types, use the bot to ask appropriate follow-up questions and we need the bot to fill up the prompt using the info provided by the user.
    Hope you can help us resolve these issues, and also give us some ideas on how to implement our use cases using Composio Actions.
    Please let us know if additional information is needed.
    Thanks!
foggy crystal
#

Hey @supple timber so just to confirm, the issue doesnt seem to be pertaining to the connection rather the subdomain name you entered. "'your%20your-domain.atlassian.net Name or service not known", could you please double check this on your side.

  1. you created the api key as follows (email:apikey) | base64 encoded
  2. the subdomain you put was just the name itself, example if my url is composio.atlassian.net simply enter composio in the input field while making the connection!
supple timber
#

We have already implemented the 2 things that you are suggesting here, however it still throwing the same error.
It is automatically picking up this as the subdomain "your%20your-domain.atlassian.net Name or service not known".
Could you please check once again and help us find the solution here?

flat hearthBOT
#

Hey Mihir, really sorry about the delayed response. Been looking into your issue, would it be possible to share the email with which you are executing these action (the email linked to your Composio account!), would really help us debug better! Will get this issue resolved asap.

supple timber
flat hearthBOT
#

Hey mihir, really sorry about this, there seems to be some infra issue causing this. Escalating this further, till this is resolved, could you try using oauth2 instead if that is a possibility to unblock yourself, will get this resolved asap!

#

Also a possible reason for this issue might be - you could have multiple accounts with the same entity id, some might be buggy - for example "your%20your-domain.atlassian.net" set as domain for executing actions.

One last thing I would suggest you to try. Delete your current integration/remove the buggy connected accounts after checking all of them and try again. Should work!

foggy crystal
#

As the error seems to be repeatedly coming from your side due to a buggy configuration of auth!

supple timber
#

Hi Samvit!
Apologies for getting back late to you.
Yes the code did start working once we cleared out multiple accounts.
Thanks a lot for your help here!