Improved Memory Attempt, Automations Created in GPT-4, Jawbone_ID Missing

ChatGPT Use cases and examples
, , , ,
1

1st time poster and a novice user.

I started a project exploring in GPT-4o how to build Custom GPTs, and I encountered an issue with automations created by GPT without my explicit instruction.

Issue Summary:

  1. During a conversation with GPT, two automations were created:
  • Hourly SBB Core Memory Backup
  • Daily SBB Good Night Summary
  1. I never instructed the GPT to create these automations, but they were triggered automatically.
  2. These automations are now firing every hour, sending me email notifications, and consuming a significant number of tokens.
  3. Unfortunately, GPT did not provide the jawbone_ID required to disable these automations and despite acknowledging that it create the automations claims to not have the IDs.
  4. I’ve tried executing Python code with the valid API key provided, to list the automations and the IDs, but it does not work.

Problem Description:

  • Without the jawbone_ID it’s impossible to disable the automations.
  • The automations are consuming tokens rapidly, and there is an urgency to stop them to prevent further issues.

File Attached:

  • Screen Shot: In GPT Mobile, the Automations appear as a widget, I have turned it off but it has not paused the automation. Also, only one of the two are visible in Mobile. NONE are visible in the GBT web interface.*

Request:

  1. Can anyone assist with finding a way to retrieve the jawbone_IDs for these automations?
  2. Is there an alternative method to disable these automations without the jawbone_ID?
  3. Am I missing something? I’ve scoured the board and so not see this issue posted.

I would greatly appreciate any guidance or a code snippet to disable these automations and stop the email notifications.

I am not an experienced developer, basic python and VBA skills, but deep experience with Excel. I can insert here the conversation from a saved text file if that helps.

2

SOLVED: The GPT created tasks, not automations, once I recognized that I was able to delete the tasks. I believe that solved the issue, still very odd that the GPT created them without authorization.